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.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/go-gitea/gitea/pull/39501 Patch, Issue Tracking
- https://github.com/go-gitea/gitea/pull/39507 Patch, Issue Tracking
- https://github.com/go-gitea/gitea/security/advisories/GHSA-94rx-fqm6-q23v Mitigation, Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 6.1 · giteaNVD modified 2026-10-13 17:59
Affected (CPE criteria) 1
cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
References 5
- https://blog.gitea.com/release-of-28.1.0/ Release Notes
- https://github.com/go-gitea/gitea/pull/39501 Patch, Issue Tracking
- https://github.com/go-gitea/gitea/pull/39507 Patch, Issue Tracking
- https://github.com/go-gitea/gitea/releases/tag/v28.1.0 Release Notes
- https://github.com/go-gitea/gitea/security/advisories/GHSA-94rx-fqm6-q23v Mitigation, Vendor Advisory