CVE-2026-121614: Docker Sandboxes host Git executes repository-controlled programs
Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.
Generated by VEDAS. Scores as of 2026-11-08 00:03 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.
What it is
Docker Sandboxes versions 0.31.0 before 0.50.0 do not neutralize repository-controlled Git configuration when running certain host-side Git commands. An attacker who can modify a host repository’s Git configuration, for example through a direct-mode sandbox with the repository mounted read-write, can configure core.fsmonitor or another Git setting that invokes an external program. Git can execute the program during a later clone-mode fetch or, starting in version 0.39.0, an sbx kit push initiated by the user. The program runs on the host with the invoking user’s permissions, outside the sandbox’s microVM isolation. The read-only host repository mount provided to a clone-mode sandbox does not itself allow that sandbox to modify the host repository’s Git configuration. The issue is fixed in version 0.50.0.
Description quoted from the CVE record (assigned by Docker, published 2026-11-03).
Weakness: CWE-15: External Control of System or Configuration Setting
How it can be exploited
Exploitable with local access with low attack complexity only when specific conditions are present needing no privileges and a user must actively take an action. Impact: confidentiality high, integrity high, availability high. CVSS:4.0/AV:L/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
CISA assessment (SSVC): CISA has no evidence of exploitation. Automatable: no. Technical impact: total.
Public exploit evidence (Exploit Observer)
Exploit Observer found 1 research write-up naming this CVE.
See all 3 references on Exploit Observer
Live scores
- EPSS
- 0.001
low predicted chance of attack - VEDAS
- 0.791
likely exploited - On CISA KEV
- Not listed
- Detection rule
- No public rule yet
Who is affected
| Product | Affected | Not affected |
|---|---|---|
| Docker Sandboxes | from 0.31.0 before 0.50.0 | Not stated |
Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.
How to fix it
Fixed versions stated in the CVE record: 0.50.0.
Vendor guidance:
- https://github.com/docker/sbx-releases/releases/tag/v0.50.0 (release-notes)
How to detect it
There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.
References
Vendor advisories and patches
- https://github.com/docker/sbx-releases/releases/tag/v0.50.0 (release-notes)
Technical analysis and advisories
- https://docs.docker.com/ai/sandboxes/security/isolation/ (technical-description)
Other references
- https://docs.docker.com/ai/sandboxes/ (product)
Other databases
Where this comes from
This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.
Supporting partners
