Quick answers
- Is CVE-2026-96594 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-96594 being exploited in the wild.
- How severe is CVE-2026-96594?
- Informational severity, published 6 October 2026.
- Which products and versions are affected?
- Gitea prior to 28.1.0.
- Is there a fix for CVE-2026-96594?
- Yes: fixed in Gitea 28.1.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-96594 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-96594?
- Check whether you run Gitea at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: Gitea 28.1.0
Technical details
The GET /api/v1/repos/{owner}/{repo}/media/{filepath} endpoint fails to set appropriate content-type and content-disposition headers when serving small files (≤1 KiB) stored directly in Git rather than Git LFS. This allows an HTML file committed to a repository to be rendered by the browser on the Gitea origin domain, enabling stored XSS. An attacker with push access can exploit this to execute JavaScript in a victim's authenticated session.
Affected products
- Gitea Gitea prior to 28.1.0
Timeline
- 2026-10-06: disclosed