Gitea accepted pushed Git trees containing two entries with the same name, which Git's own consistency checks reject. Gitea's web views resolved such a path to the first entry, while `git checkout`, Gitea Actions, and release archives use the last. A contributor could open a pull request whose diff and file views show benign content while CI and checkouts at the same commit use different, attacker-controlled content. Incoming objects are now checked for consistency; objects already stored in existing repositories are not rescanned.
Fix
Patch, vendor advisory and mitigation references on NVD 2
- https://github.com/go-gitea/gitea/pull/39472 Patch
- https://github.com/go-gitea/gitea/security/advisories/GHSA-6pv5-8rp7-8c75 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 9.1 · giteaNVD modified 2026-10-13 16:27
Affected (CPE criteria) 1
cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*
References 4
- https://blog.gitea.com/release-of-28.0.0/ Release Notes
- https://github.com/go-gitea/gitea/pull/39472 Patch
- https://github.com/go-gitea/gitea/releases/tag/v28.0.0 Release Notes
- https://github.com/go-gitea/gitea/security/advisories/GHSA-6pv5-8rp7-8c75 Mitigation, Vendor Advisory