CVE-2026-20897: Gitea does not properly validate repository ownership when deleting Git LFS locks
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.
Published Jan 23, 2026
Affected packages
github.com/go-gitea/gitea
- Ecosystem
- Go
- Affected
- < 1.25.4
- Fixed in
- 1.25.4
- Check
go list -m github.com/go-gitea/gitea
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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.
References
- https://nvd.nist.gov/vuln/detail/CVE-2026-20897
- https://github.com/go-gitea/gitea/pull/36344
- https://github.com/go-gitea/gitea/pull/36349
- https://blog.gitea.com/release-of-1.25.4
- https://github.com/go-gitea/gitea/releases/tag/v1.25.4
- https://github.com/go-gitea/gitea/commit/da036f3f35ca830b22cf4480912ed261303b798f
- https://github.com/advisories/GHSA-393c-qgvj-3xph
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Go vulnerabilities
All Go entriesCVE-2026-25779
Gitea: Open Redirect via redirect_to
medium5.1Jun 17, 2026CVE-2026-20750
Gitea does not properly validate project ownership in organization project operations
medium5.3Jan 23, 2026CVE-2026-20800
Gitea improperly exposes issue and pull request titles
low2.3Jan 23, 2026CVE-2026-20883
Gitea improperly exposes issue titles and repository names through previously started stopwatches
low2.3Jan 23, 2026CVE-2026-20888
Gitea does not properly verify authorization when canceling scheduled auto-merges via the web interface
medium5.3Jan 23, 2026CVE-2026-20904
Gitea does not properly validate ownership when toggling OpenID URI visibility
medium5.3Jan 23, 2026
