CVE-2026-20897Network attack vectorHinoki check available

Cross-repository lock deletion via ID-only lookup

Published Jan 22, 2026 · Updated Jan 22, 2026

Broken access control in Gitea 1.25.3 and earlier allows remote authenticated users to delete Git LFS locks across repositories. DeleteLFSLockByID retrieves the lock using only its numeric ID, without constraining the database query to the repository named by the request. Write access to any repository is sufficient to remove another repository's lock, disrupting its LFS coordination without reading or changing file content.

CVSS severity5.3
Medium
EPSS probability0.43%
Next 30 days · Sep 16, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Book a demo

Summary

What happened

Broken access control in Gitea 1.25.3 and earlier allows remote authenticated users to delete Git LFS locks across repositories. DeleteLFSLockByID retrieves the lock using only its numeric ID, without constraining the database query to the repository named by the request. Write access to any repository is sufficient to remove another repository's lock, disrupting its LFS coordination without reading or changing file content.

The record

CVE
CVE-2026-20897
Published
Jan 22, 2026
Updated
Jan 22, 2026
Vendor
Gitea
Product
Gitea
Classifications
CWE-639, CWE-284, T1565.001
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Jan 22, 2026CVE publishedPublication date reported by the CVE source.
  2. Jan 22, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <=1.25.3

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

Gitea · Giteaversion=0 <=1.25.3

Published CVSS scores

9.1CISA-ADPCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
5.3GitHubCVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:N
9.1redhat-SADPCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 10, 2026Sep 16, 2026
Latest reporting daySep 16, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-639Authorization Bypass Through User-Controlled Key
CWE-284Improper Access Control
T1565.001Stored Data Manipulation

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.

Book a demo