Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-393c-qgvj-3xph | Gitea does not properly validate repository ownership when deleting Git LFS locks |
Thu, 29 Jan 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:gitea:gitea:*:*:*:*:*:-:*:* |
Tue, 27 Jan 2026 00:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| References |
| |
| Metrics |
threat_severity
|
threat_severity
|
Fri, 23 Jan 2026 22:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
cvssV3_1
|
Fri, 23 Jan 2026 16:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Gitea
Gitea gitea |
|
| Vendors & Products |
Gitea
Gitea gitea |
Thu, 22 Jan 2026 23:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | Gitea Git LFS Lock Deletion Broken Access Control (Cross-Repo IDOR) | |
| Weaknesses | CWE-284 CWE-639 |
|
| References |
|
Status: PUBLISHED
Assigner: Gitea
Published:
Updated: 2026-01-23T21:54:06.525Z
Reserved: 2026-01-08T23:02:37.525Z
Link: CVE-2026-20897
Updated: 2026-01-23T17:56:49.022Z
Status : Analyzed
Published: 2026-01-22T22:16:18.960
Modified: 2026-01-29T22:02:20.170
Link: CVE-2026-20897
OpenCVE Enrichment
Updated: 2026-04-18T15:30:03Z
Github GHSA