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.
01
describes (1)
Related CVEs.
| ID | severity | exploitable | ||
|---|---|---|---|---|
| CVE-2026-20897US | — | — | ||
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 rep… | ||||
02
references
External citations — patches, advisories, analysis.
- https://blog.gitea.com/release-of-1.25.4WEB
- https://github.com/go-gitea/giteaPACKAGE
- https://github.com/go-gitea/gitea/commit/da036f3f35ca830b22cf4480912ed261303b798fWEB
- https://github.com/go-gitea/gitea/pull/36344WEB
- https://github.com/go-gitea/gitea/pull/36349WEB
- https://github.com/go-gitea/gitea/releases/tag/v1.25.4WEB
- https://nvd.nist.gov/vuln/detail/CVE-2026-20897ADVISORY
scry
Advisories like this name the exposed products attackers go after on your perimeter. See what is exposed on your perimeter with a free passive scan.
Free scan