Vulnerability advisory

CVE-2026-24451

Gitea fork synchronization can expose private parent repository data

Published Updated OSV record ↗

Also known as GHSA-wrf9-r3h7-7x5vGO-2026-6081

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

Affected versions

Repository

Affected commitsFixed by commit
GIT github.com/go-gitea/gitea ↗
2c749ce548b1da0a52835861a87b888e67842d29 to before 4aa0d704f2c7d30351016b740bfc45247fd77efa4aa0d704f2c7d30351016b740bfc45247fd77efa
Also listed as affected (2)
  • 1.26.2
  • v1.26.2

Description

Gitea 1.26.2 allows fork synchronization to continue after a parent repository changes from public to private, exposing data to a fork that should no longer be authorized.

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