CVE-2026-24451: Gitea Open Source Git Server · Information Exposure
Affects Gitea Open Source Git ServerSource CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 3 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| GiteaGitea Open Source Git Server | Affected
| Fixed in– |
GitHubgo-gitea/giteapkg:github/go-gitea/giteaOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until a fix is available, administrators should manually verify repository visibility changes and consider restricting fork synchronization or access to forks when parent repositories are made private.
Description
Gitea version 1.26.2 contains a vulnerability where fork synchronization continues even after the parent repository's visibility changes from public to private. This behavior exposes data in the fork repository that should no longer be accessible, leading to unauthorized information disclosure.