BaseFortify

Publication date: 2026-01-22

Last updated on: 2026-06-27

Assigner: Gitea Limited

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 Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published

2026-01-22

Last Modified

2026-06-27

Generated

2026-07-06

AI Q&A

2026-01-23

EPSS Evaluated

2026-07-05

NVD

CVE-2026-20897

Affected Vendors & Products

Vendor	Product	Version / Range
gitea	gitea	to 1.25.4 (exc)

Helpful Resources

Exploitability

CWE

KEV

CWE ID	Description
CWE-284	The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor.
CWE-639	The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

Executive Summary

This vulnerability in Gitea occurs because the system does not properly validate repository ownership when deleting Git LFS locks. As a result, a user who has write access to one repository may be able to delete LFS locks that belong to other repositories, which they should not have permission to modify.

Impact Analysis

The impact of this vulnerability is that unauthorized users with write access to one repository could delete Git LFS locks on other repositories. This could disrupt collaboration and version control processes by allowing users to interfere with locks that protect files in other repositories, potentially leading to data integrity issues or workflow interruptions.

Hi! I’m here to help you understand CVE-2026-20897. Ask me anything about the vulnerability, its impact, or mitigation strategies.

0/70