Vulnerability in Gitea

[ Description ]Official description

The Gitea API endpoint `GET /api/v1/repos/{owner}/{repo}/media/{filepath}` wrote files of up to 1 KiB that are stored directly in Git, not in LFS, to the response without the content type and disposition headers Gitea uses for user content. An HTML file committed to a repository was therefore rendered by the browser on the Gitea origin. A user who can push to a repository could run JavaScript in the session of a victim who opens the media URL and act with the victim's permissions.

[ Fixes ]Fixes and patches

• Patch on github.comVendor patch or bulletin · NVD · Reference tagged 'Patch' by NVD
• Patch on github.comVendor patch or bulletin · NVD · Reference tagged 'Patch' by NVD

[ Advisories ]Government CERT advisories

• BSI CERT-Bund6 Oct 2026WID-SEC-2026-3792

  Gitea: Multiple vulnerabilities Translated from German

  CVE-2026-103670CVE-2026-94205CVE-2026-103059+26 more CVEs

[ References ]References

• blog.gitea.com/release-of-28.1.0Release Notes
• github.com/go-gitea/gitea/pull/39501PatchIssue Tracking
• github.com/go-gitea/gitea/pull/39507PatchIssue Tracking
• github.com/go-gitea/gitea/releases/tag/v28.1.0Release Notes
• github.com/go-gitea/gitea/security/advisories/GHSA-94rx-fqm6-q23vMitigationVendor Advisory