Gitea Git LFS Lock Deletion Broken Access Control (Cross-Repo IDOR)
28Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 9.1epss 0.4%
exploitation probability
0.4%top 66% of all CVEs
observed exploitation
nono source reports it
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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Affected products
Gitea · Gitea Open Source Git ServerReferences
https://access.redhat.com/security/cve/CVE-2026-20897https://blog.gitea.com/release-of-1.25.4/https://bugzilla.redhat.com/show_bug.cgi?id=2432204https://github.com/go-gitea/gitea/pull/36344https://github.com/go-gitea/gitea/pull/36349https://github.com/go-gitea/gitea/releases/tag/v1.25.4https://github.com/go-gitea/gitea/security/advisories/GHSA-rrq5-r9h5-pc7chttps://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-20897.json