Vulnerabilities · 2026 · Gitea
CVE-2026-20897
Gitea vulnerability
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.
High priority: this vulnerability is rated critical and can be attacked over the network without a login.
Affected products
Gitea. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Gitea runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/go-gitea/gitea/pull/36344 · Patch
- github.com/go-gitea/gitea/pull/36349 · Patch
- blog.gitea.com/release-of-1.25.4/
- github.com/go-gitea/gitea/releases/tag/v1.25.4
- github.com/go-gitea/gitea/security/advisories/GHSA-rrq5-r9h5-pc7c
- nvd.nist.gov/vuln/detail/CVE-2026-20897
- blog.gitea.com/release-of-1.25.4
- github.com/go-gitea/gitea/commit/da036f3f35ca830b22cf4480912ed261303b798f
- nvd.nist.gov/vuln/detail/CVE-2026-20897
- cve.org/CVERecord?id=CVE-2026-20897
More vulnerabilities in Gitea products
CVE-2026-20912CVE-2026-20904CVE-2026-20888CVE-2026-20883CVE-2026-20800CVE-2026-20750CVE-2026-20736CVE-2026-0798All 52
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.