CVE-2026-20897 | Gitea Git LFS Lock Deletion Broken Access Control (Cross-Repo IDOR)

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: 2026-01-22 Last update: 2026-01-29 Assigner: 88ee5874-cf24-4952-aea0-31affedb7ff2 Source: 88ee5874-cf24-4952-aea0-31affedb7ff2
NVD Status：Analyzed，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2026-20897 is rated Low Risk (37.5/100): CVSS Critical severity, with low exploitation likelihood (EPSS 0.02%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2026-20897

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-01-23 — 0.02% —

Full EPSS history (1 record total)

Common vulnerability scoring system (CVSS) metrics for CVE-2026-20897

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.1 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 3.9 5.2 134c704f-9b21-4f2e-91b3-4a467353bcc0

Weakness enumeration for CVE-2026-20897

GitHub Security Advisory for CVE-2026-20897

GHSA-393c-qgvj-3xph · Severity: medium · Ecosystem: go — Gitea does not properly validate repository ownership when deleting Git LFS locks

OS Trackers for CVE-2026-20897

vendor priority summary link
alpine — CVE-2026-20897: 1 source package rows (gitea); 44 state rows across 2 repos (3.23-community, edge-community); fixed 0, open 44. https://security.alpinelinux.org/vuln/CVE-2026-20897
redhat critical — https://access.redhat.com/security/cve/CVE-2026-20897

Affected software / configurations for CVE-2026-20897

Vendor Product Version Raw CPE
gitea gitea < 1.25.4 cpe:2.3:a:gitea:gitea:*:*:*:*:*:-:*:*

References for CVE-2026-20897

cvelogic Threat Intelligence