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

> Attackers can access private parent repository data via fork synchronization after the parent repository becomes private.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 3 Jul 2026
- **Updated:** 7 Jul 2026
- **Also known as:** GHSA-wrf9-r3h7-7x5v, GO-2026-6081

## What is CVE-2026-24451?

CVE-2026-24451 is a high-severity vulnerability in Gitea Open Source Git Server, published on 3 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

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

Weakness: CWE-284 (Improper Access Control), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2026-24451?

3 open source packages ship an affected version, including code.gitea.io/gitea.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `code.gitea.io/gitea` | Go | All versions | 1.26.3 |
| `code.gitea.io/gitea` | Go | All versions | 1.26.3 |
| `code.gitea.io/gitea` | Go | All versions | 1.26.3 |

## How do I fix CVE-2026-24451?

Upgrade code.gitea.io/gitea to 1.26.3 or later.

## Is CVE-2026-24451 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24451 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-24451 and fix it if it is affected.

What it is: CVE-2026-24451 is a high-severity vulnerability in Gitea Open Source Git Server, published on 3 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-24451 exists.

Affected packages and fixed versions:
- code.gitea.io/gitea (Go): affected all versions; fixed in 1.26.3
- code.gitea.io/gitea (Go): affected all versions; fixed in 1.26.3
- code.gitea.io/gitea (Go): affected all versions; fixed in 1.26.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-24451/ (Markdown: https://insights.sbomify.com/CVE-2026-24451/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-24451
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-24451
- OSV: https://osv.dev/vulnerability/CVE-2026-24451

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-24451/
Summaries are generated and may contain mistakes; the official description above is the record.