DemoBook a demo

Vulnerability advisory

BIT-gitea-2026-20897

Gitea Git LFS Lock Deletion Broken Access Control (Cross-Repo IDOR)

Published Updated OSV record ↗

Also known as CVE-2026-20897GHSA-393c-qgvj-3xphGHSA-rrq5-r9h5-pc7cGO-2026-4363

Severity

Severity not reported.

Affected versions

gitea Bitnami

AffectedFixed in
All versions before 1.25.41.25.4

Severity for this package

  • CVSS 3.xCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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.

References

  • Codex
  • Claude Code
  • VS Code
  • GitHub Copilot
  • Cursor
  • Cline
  • Windsurf
  • Google Anti-gravity
  • OpenCode
  • Pi
  • Gemini CLI
  • Hermes Agent
  • Zed
  • Junie
  • Qwen Code
  • Kiro
  • Kilo Code
  • Factory Droid

Set up GitHits for your agents

Run this command:

<> bash
npx githits@latest init

What happens next:

  1. Opens your browser to authorize GitHits
  2. Asks whether to set up GitHits at the user or project level
  3. Detects your supported AI coding tools
  4. Lets you choose which tools to configure
  5. Configures the selected tools

Having trouble? Check our documentation.