Gitea repository media API stored XSS
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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-96594US | — | — | ||
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 conte… | ||||
02
references
External citations — patches, advisories, analysis.
- https://blog.gitea.com/release-of-28.1.0/ARTICLE
- https://github.com/go-gitea/gitea/pull/39501FIX
- https://github.com/go-gitea/gitea/pull/39507FIX
- https://github.com/go-gitea/gitea/releases/tag/v28.1.0ARTICLE
- https://github.com/go-gitea/gitea/security/advisories/GHSA-94rx-fqm6-q23vADVISORY
- https://nvd.nist.gov/vuln/detail/CVE-2026-96594WEB
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan