CVE-2026-20897GHSA-393C-QGVJ-3XPHBIT-GITEA-2026-20897GHSA-RRQ5-R9H5-PC7CGO-2026-4363
Gitea Git LFS Lock Deletion Broken Access Control (Cross-Repo IDOR)
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.25.4
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
Gitea does not properly validate repository ownership when deleting Git LFS locks. A user with write access to one repository may be able to delete LFS locks belonging to other repositories.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- Gitea Gitea Open Source Git Server
through 1.25.3
- github.com/go-gitea/giteaGo
fixed in 1.25.4
- code.gitea.io/giteaGo
fixed in 1.25.4