How severe is CVE-2026-104026?

CVE-2026-104026 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2026-104026 being actively exploited?

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

How do I fix CVE-2026-104026?

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

When was CVE-2026-104026 published?

CVE-2026-104026 was published on 2026-10-02.

CVE-2026-104026

CVE-2026-104026 is a high-severity vulnerability with a CVSS 3.x base score of 7.8. 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-150.

Key facts

Severity: High (CVSS 3.x base score 7.8)
EPSS exploit prediction: 0% (2nd percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-150
Published: 2026-10-02
Last modified: 2026-10-02

Description

In Sapling SCM prior to v0.2.20260929-102736, control characters were allowed to be embedded in Git subtree URLs. A maliciously constructed repository, if cloned by a target, could trigger code execution on otherwise read-only actions such as sl log/blame/annotate.

Frequently asked questions

What is CVE-2026-104026?: In Sapling SCM prior to v0.2.20260929-102736, control characters were allowed to be embedded in Git subtree URLs. A maliciously constructed repository, if cloned by a target, could trigger code execution on otherwise read-only actions such as sl log/blame/annotate.
How severe is CVE-2026-104026?: CVE-2026-104026 has a CVSS 3.x base score of 7.8, rated high severity. It is exploitable over local access with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2026-104026 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (2nd percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-104026?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2026-104026 published?: CVE-2026-104026 was published on 2026-10-02.

References

https://www.facebook.com/security/advisories/cve-2026-104026

Other CWE-150 vulnerabilities

CVE-2022-30123 — Critical (CVSS 10.0): A sequence injection vulnerability exists in Rack <2.0.9.1, <2.1.4.1 and <2.2.3.1 which could allow is a possible shell…
CVE-2020-6932 — Critical (CVSS 10.0): An information disclosure and remote code execution vulnerability in the slinger web server of the BlackBerry QNX…
CVE-2025-47284 — Critical (CVSS 9.9): Gardener implements the automated management and operation of Kubernetes clusters as a service. A security…
CVE-2023-26055 — Critical (CVSS 9.9): XWiki Commons are technical libraries common to several other top level XWiki projects. Starting in version…
CVE-2026-25996 — Critical (CVSS 9.8): Inspektor Gadget is a set of tools and framework for data collection and system inspection on Kubernetes clusters and…
CVE-2025-25286 — Critical (CVSS 9.8): Crayfish is a collection of Islandora 8 microservices, one of which, Homarus, provides FFmpeg as a microservice. Prior…

Browse all CWE-150 vulnerabilities →