CVE-2026-20897

CRITICALNVD 9.19.1—

9.1

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 v3: 9.1
EG Score: 9.1(medium)
EPSS: 6.2%
KEV: Not listed

Published

January 22, 2026

Last Modified

January 29, 2026

References (5)

88ee5874-cf24-4952-aea0-31affedb7ff2https://blog.gitea.com/release-of-1.25.4/
88ee5874-cf24-4952-aea0-31affedb7ff2https://github.com/go-gitea/gitea/pull/36344
88ee5874-cf24-4952-aea0-31affedb7ff2https://github.com/go-gitea/gitea/pull/36349
88ee5874-cf24-4952-aea0-31affedb7ff2https://github.com/go-gitea/gitea/releases/tag/v1.25.4
88ee5874-cf24-4952-aea0-31affedb7ff2https://github.com/go-gitea/gitea/security/advisories/GHSA-rrq5-r9h5-pc7c

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 16× in last 7d / 16× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-04 13:12 UTCepss_batch
2026-06-04 13:12 UTCepss_batch
2026-06-04 13:12 UTCepss_batch
2026-06-02 20:13 UTCepss_batch
2026-06-02 20:13 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-06-01 13:51 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 22:30 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-31 00:16 UTCepss_batch
2026-05-29 15:24 UTCEG score recompute
2026-05-29 13:44 UTCepss_batch
2026-05-29 13:44 UTCepss_batch

Frequently asked(5)

What is CVE-2026-20897?

CVE-2026-20897 is a critical vulnerability published on January 22, 2026. 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.

When was CVE-2026-20897 disclosed?

CVE-2026-20897 was first published in the National Vulnerability Database on January 22, 2026, with the most recent update on January 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2026-20897 actively exploited?

CVE-2026-20897 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 6.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2026-20897?

CVE-2026-20897 has a CVSS v3 base score of 9.1 (NVD).

How do I remediate CVE-2026-20897?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-20897, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-20897

Explore →

Is Your Infrastructure Affected by CVE-2026-20897?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2026-20897

📅 Published

🔄 Last Modified

🔗 References (5)

Weakness Classification(2)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2026-20897?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (5)

Frequently asked(5)

Related CVEs(same CWE)