| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.2 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in Gitea up to 1.25.3. Affected by this issue is some unknown functionality. Executing a manipulation can lead to access control. This vulnerability appears as CVE-2026-20897. The attack may be performed from remote. There is no available exploit. Upgrading the affected component is recommended.
Details
A vulnerability has been found in Gitea up to 1.25.3 and classified as critical. This vulnerability affects an unknown code block. The manipulation with an unknown input leads to a access control vulnerability. The CWE definition for the vulnerability is CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. As an impact it is known to affect integrity, and availability. CVE summarizes:
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.
The advisory is shared for download at github.com. This vulnerability was named CVE-2026-20897 since 01/09/2026. The exploitation appears to be easy. The attack can be initiated remotely. There are neither technical details nor an exploit publicly available. The MITRE ATT&CK project declares the attack technique as T1068.
Upgrading to version 1.25.4 eliminates this vulnerability. The upgrade is hosted for download at github.com. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
The vulnerability is also documented in the databases at EUVD (EUVD-2026-4264) and CERT Bund (WID-SEC-2026-0200). Once again VulDB remains the best source for vulnerability data.
Affected
- Open Source Gitea
Product
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.4VulDB Meta Temp Score: 5.2
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Gitea 1.25.4
Patch: github.com
Timeline
01/09/2026 CVE reserved01/23/2026 Advisory disclosed
01/23/2026 VulDB entry created
01/24/2026 VulDB entry last update
Sources
Advisory: GHSA-rrq5-r9h5-pc7cStatus: Confirmed
CVE: CVE-2026-20897 (🔒)
GCVE (CVE): GCVE-0-2026-20897
GCVE (VulDB): GCVE-100-342508
EUVD: 🔒
CERT Bund: WID-SEC-2026-0200 - Gitea: Mehrere Schwachstellen
Entry
Created: 01/23/2026 08:08Updated: 01/24/2026 09:06
Changes: 01/23/2026 08:08 (56), 01/24/2026 07:02 (1), 01/24/2026 09:06 (7)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.