CVE-2026-121614
Docker Sandboxes host Git executes repository-controlled programs
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.
Fixes and workarounds
Fix
Upgrade Docker Sandboxes to version 0.50.0 or later.
Source: CNA: DockerWorkaround
Until upgrading, do not run clone-mode sandbox creation or start, or sbx kit push, in repositories whose Git configuration or .git metadata can be modified by untrusted code, such as a repository mounted read-write into another sandbox.
Source: CNA: DockerAffected products and versions
| Product | Versions | Authority |
|---|---|---|
| Docker Sandboxes Docker Platforms: MacOS, Linux, Windows |
≥ 0.31.0; < 0.50.0 (affected, semver)
Other versions: unaffected |
CNA: Docker |
Version ranges are source assertions. Check the vendor advisory and your installed configuration before determining exposure.
CVSS assessments
| Version / score | Vector | Authority |
|---|---|---|
| 4.0 / 7.1 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 | CNA: Docker |
| 4.0 / 7.1 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X | NVD: [email protected] |
Exploit evidence
No exploit evidence in collected sources. This is not proof of no exploitation.
References
- https://docs.docker.com/ai/sandboxes/CNA: Docker · product
- https://docs.docker.com/ai/sandboxes/security/isolation/CNA: Docker · technical-description
- https://github.com/docker/sbx-releases/releases/tag/v0.50.0CNA: Docker · release-notes
- https://docs.docker.com/ai/sandboxes/[email protected]
- https://docs.docker.com/ai/sandboxes/security/isolation/[email protected]
- https://github.com/docker/sbx-releases/releases/tag/v0.50.0[email protected]
For agents and automation
Read public disclosures for free as Markdown or JSON. Compatible browsers also expose native WebMCP tools to search disclosures, read this page, and discover API access.
Use the ontology-linked Cyber API with x402 pay per request, or a Y2 Pro or Elite API key with the intel:cyber scope.
Endpoints and access details
https://api.y2.dev/api/v2/cyber/cveshttps://api.y2.dev/api/v2/cyber/cves/{cveId}
A workspace owner or admin can create a Pro or Elite API key. Send Authorization: Bearer <Y2_API_KEY> from your trusted agent runtime.
For x402, omit Authorization and read the HTTP 402 payment challenge before signing a retry. Public browser tools do not make payments.