How severe is CVE-2026-95106?

CVE-2026-95106 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.

Is CVE-2026-95106 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (21st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-95106?

CVE-2026-95106 affects Gitea. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-95106?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

When was CVE-2026-95106 published?

CVE-2026-95106 was published on 2026-10-06 and last updated on 2026-10-13.

CVE-2026-95106

CVE-2026-95106 is a critical-severity vulnerability in Gitea with a CVSS 3.x base score of 9.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-706.

Key facts

Severity: Critical (CVSS 3.x base score 9.1)
EPSS exploit prediction: 0% (21st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-706
Affected product: Gitea
Published: 2026-10-06
Last modified: 2026-10-13

Description

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 checked for consistency; objects already stored in existing repositories are not rescanned.

Frequently asked questions

What is CVE-2026-95106?: 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 checked for consistency; objects already stored in existing repositories are not rescanned.
How severe is CVE-2026-95106?: CVE-2026-95106 has a CVSS 3.x base score of 9.1, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability none.
Is CVE-2026-95106 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (21st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-95106?: CVE-2026-95106 affects Gitea. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-95106?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
When was CVE-2026-95106 published?: CVE-2026-95106 was published on 2026-10-06 and last updated on 2026-10-13.

References

Affected products (1)

cpe:2.3:a:gitea:gitea:*:*:*:*:*:*:*:*

More vulnerabilities in Gitea

CVE-2026-94205 — Critical (CVSS 9.8): Gitea Actions decided whether a fork pull request run needed approval based on the user who triggered the event rather…
CVE-2026-73278 — Critical (CVSS 9.8): Gitea's OAuth2 and OpenID Connect sign-in paths do not require a WebAuthn challenge when WebAuthn is the account's only…
CVE-2026-60004 — Critical (CVSS 9.8): Gitea before 1.27.1 allows remote code execution via the diffpatch API through Git hook installation.
CVE-2022-42968 — Critical (CVSS 9.8): Gitea before 1.17.3 does not sanitize and escape refs in the git backend. Arguments to git commands are mishandled.
CVE-2021-45331 — Critical (CVSS 9.8): An Authentication Bypass vulnerability exists in Gitea before 1.5.0, which could let a malicious user gain privileges.…
CVE-2021-45330 — Critical (CVSS 9.8): An issue exsits in Gitea through 1.15.7, which could let a malicious user gain privileges due to client side cookies…

All CVEs affecting Gitea →

Other CWE-706 vulnerabilities

CVE-2026-65816 — Critical (CVSS 10.0): Use of incorrectly-resolved name or reference in Azure Arc allows an unauthorized attacker to elevate privileges over a…
CVE-2026-92262 — Critical (CVSS 9.9): MariaDB server is a community developed fork of MySQL server. From 10.6.1 until 10.6.28, 10.11.19, 11.4.13, 11.8.9,…
CVE-2026-92951 — Critical (CVSS 9.9): vm2 before 3.11.7 contains an incorrect authorization vulnerability in the external package allowlist check that uses…
CVE-2025-65474 — Critical (CVSS 9.8): An arbitrary file rename vulnerability in the /admin/manager.php component of EasyImages 2.0 v2.8.6 and below allows…
CVE-2024-35198 — Critical (CVSS 9.8): TorchServe is a flexible and easy-to-use tool for serving and scaling PyTorch models in production. TorchServe 's check…
CVE-2023-31814 — Critical (CVSS 9.8): D-Link DIR-300 firmware <=REVA1.06 and <=REVB2.06 is vulnerable to File inclusion via /model/__lang_msg.php.

Browse all CWE-706 vulnerabilities →

Threat intelligence

Threat-intel indicators referencing this CVE:

117.24.243.99 (ipv4-addr)