Critical severity · published Jan 22, 2026
CVE-2026-20897
Gitea does not properly validate repository ownership when deleting Git LFS locks
9.1
CVSS
0.5%
EPSS
No
On KEV
Description
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 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.5% · higher than 39% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
GI
Gitea · Gitea
before 1.25.4 · source: NVD
References
NVD
https://nvd.nist.gov/vuln/detail/CVE-2026-20897
CVE.org
https://www.cve.org/CVERecord?id=CVE-2026-20897
Release Notes
https://blog.gitea.com/release-of-1.25.4/
Issue Tracking
https://github.com/go-gitea/gitea/pull/36344
Issue Tracking
https://github.com/go-gitea/gitea/pull/36349
Release Notes
https://github.com/go-gitea/gitea/releases/tag/v1.25.4
Broken Link
https://github.com/go-gitea/gitea/security/advisories/GHSA-rrq5-r9h5-pc7c
access.redhat.com
https://access.redhat.com/security/cve/CVE-2026-20897
More from Gitea
9.8
CVE-2026-60004
Gitea Code Injection Vulnerability
9.8
CVE-2026-59774
Gitea Org-mode file disclosure and code execution
9.8
CVE-2026-73278
Gitea WebAuthn bypass during OAuth and OIDC sign-in
9.8
CVE-2026-94205
Gitea fork workflow approval bypass through maintainer-triggered events
9.8
CVE-2022-42968
Gitea before 1.17.3 does not sanitize and escape refs in the git backend