CVE-2026-20897 — Improper Access Control in Gitea

CWE-284 — Improper Access ControlCWE-639 — Authorization Bypass Through User-Controlled Key6 documents5 sources
Severity
9.1CRITICALNVD
EPSS
0.0%
top 96.72%
CISA KEV
Not in KEV
Exploit
No known exploits
Affected products
4
Code.gitea.io GiteaGithub.com Go-gitea GiteaGitea+1 more
Timeline
PublishedJan 22
Latest updateFeb 2

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:NExploitability: 3.9 | Impact: 5.2

Affected Packages4 packages

▶NVDgitea/gitea< 1.25.4
▶Gocode.gitea.io/gitea< 1.25.4

Patches

Patch: github.com ↗Patch: github.com ↗

🔴Vulnerability Details

3
OSV
Gitea does not properly validate repository ownership when deleting Git LFS locks in code.gitea.io/gitea↗2026-02-02
▶
GHSA
Gitea does not properly validate repository ownership when deleting Git LFS locks↗2026-01-23
▶
OSV
Gitea does not properly validate repository ownership when deleting Git LFS locks↗2026-01-23
▶

📋Vendor Advisories

1
Red Hat
gitea: Gitea Git LFS Lock Deletion Broken Access Control (Cross-Repo IDOR)↗2026-01-22
▶

🕵️Threat Intelligence

1
Wiz
CVE-2026-20897 Impact, Exploitability, and Mitigation Steps | Wiz↗
▶