CVE-2026-20897Disclosure(gitea / gitea)

LOWCVSS 9.1 · CRITICAL

Signal is active with 1 mentions in latest observed window

Immediate actions

  • Patch gitea gitea systems immediately

Recommended action window: Monitor and triage in normal cycle

NVD 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.

0.5/ 10 priority

Sources & remediation

Weakness type (CWE)
CWE-284CWE-639

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

AVAILABLE

Momentum

NONE

Are you affected?

If you run products in this scope, you should treat this CVE as relevant to your environment.

  • gitea

Threat summary

  • Patch or workaround signal is available
  • 1 mentions across 1 observed day

What's happening

  • Patch or workaround mentioned in 1 signal
  • Technical details provided in 1 signal
  • Disclosure: 1 classified signal
  • 1 total mentions across 1 day

Affected systems

Vendors
Products
gitea

Deep dive

Activity timeline1 mentions / 1d
00111Mentions · 2026-01-30: 1Patch / Workaround · 2026-01-30: 1Technical Details · 2026-01-30: 101-30
Signal classification1 categories
Disclosure
1100.0%
Referenced assets1 URL
By indicator
Full discourse1 post
  • PulsePatch.io@pulsepatchio
    Disclosure

    A broken access control flaw (CVE-2026-20897) in Gitea affects Git LFS lock deletion. An authenticated user could delete cross-repository LFS locks. Review and update Gitea instances. #Gitea #GitLFS #InfoSec https://www.pulsepatch.io/posts/cve-2026-20897-gitea-git-lfs-lock-deletion-idor

    Post summary

    A broken access control flaw (CVE-2026-20897) in Gitea lets authenticated users delete cross‑repository Git LFS locks; administrators should review and update their installations to remediate the issue.

    0000041
    1 followersView on X
CPE platform detail1 entries

1 of 1 entries

PartVendorProductVersionTarget SWTarget HW
Appgiteagitea---

Explore more