CVE-2026-104026: Meta Platforms Sapling SCM · Improper Neutralization of Escape, Meta, or Control Sequences
Affects Meta Platforms Sapling SCMSource CVE Database V5
Not known to be exploited · CVSS 7.8 High : upgrade to v0.2.20260929-102736 soon.
Data as of 15 Nov 2026, 20:25 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 2% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in v0.2.20260929-102736
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Oct 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
Upgrade Meta Platforms Sapling SCM to v0.2.20260929-102736.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Meta Platforms, IncSapling SCM | Affected
| Fixed in
|
AI-suggested
A fix is available in Sapling SCM version 0.2.20260929-102736 and later. Users should upgrade to this version or newer to remediate the vulnerability. No additional mitigation steps are indicated.
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.