PatchTheCVECVE-2026-95106: Gitea accepted pushed Git trees containing two entries with the same name, which Git's own consistency checks
CVE-2026-95106 is a critical-severity flaw (CVSS 9.1) affecting gitea. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
Gitea accepted pushed Git trees containing two entries with the same name, which Git's own consistency checks reject. Gitea's web views resolved such a path to the first entry, while `git checkout`, Gitea Actions, and release archives use the last. A contributor could open a pull request whose diff and file views show benign content while CI and checkouts at the same commit use different, attacker-controlled content. Incoming objects are now chec
Why this priority
- Critical severity
- Remotely exploitable, no login, no user action
A fixed release or distro patch exists.
Risk facts
| CVSS score | 9.1 (Critical) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | None |
| EPSS exploit chance | 0.3% (top 74%) |
| CISA exploited list | No |
| Weakness | CWE-706 |
| Published | 2026-10-06 |
| Last modified | 2026-10-13 |
Last updated 2026-10-13 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2026-95106?
gitea: upgrade to 28.0.0. Exact commands for each OS are on this page.
Is CVE-2026-95106 being exploited?
CVE-2026-95106 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2026-95106 affect?
CVE-2026-95106 affects gitea. Severity is critical (CVSS 9.1). Gitea accepted pushed Git trees containing two entries with the same name, which Git's own consistency checks reject. Gitea's web views resolved such a path to the first entry, while `git checkout`, Gitea Actions, and release archives use t
How urgent is CVE-2026-95106?
Priority 43/100. Critical severity; Remotely exploitable, no login, no user action
Software pages
Git vulnerabilities · Gitea vulnerabilities
Related CVEs
- CVE-2026-101027 HIGH 7.7 UPGRADE When `[migrations] ALLOWED_DOMAINS` was configured, a hostname matching the allow list was accepted without ch
- CVE-2026-101029 MEDIUM 4.3 UPGRADE Gitea's repository migration and pull mirror egress checks could be bypassed with a hostname that returns mult
- CVE-2026-103059 CRITICAL 9.1 UPGRADE When Gitea's built-in SSH server is enabled (`START_SSH_SERVER = true`), the presented public key was looked u
- CVE-2026-103667 MEDIUM 5.4 UPGRADE Gitea's container registry served blob downloads with a `Content-Type` taken from the media type declared in p
- CVE-2026-103670 HIGH 7.5 UPGRADE When a Gitea Actions run was inserted, older runs in the same workflow-level concurrency group were cancelled