Docker Sandboxes host Git executes repository-controlled programs
Affects Docker Sandboxes from 0.31.0 before 0.50.0 when the sandbox directly mounts the host workspace, giving the agent read-write access to the host repository. Fixed in 0.50.0.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
- Exploited
- No known exploitation
- Fix
- Fixed in 0.50.0
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. The sandbox uses a direct mount of the host workspace, giving the agent read-write access to the host repository.
- Exploitation?/40Exploitation: unknown (data gap). No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach17/20Affects Docker (a widely deployed server, runtime, framework or database)
- Severity7.1/10CVSS 7.1
- No patch0/5No signal
What would change the score
- Would score about 79 if added to CISA KEV
- Would score about 74 if CISA's SSVC rates exploitation active
- Would score about 39 if CISA's SSVC rates it automatable
CVE-2026-121614 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.1 (high) and affects Docker Sandboxes; fixed in 0.50.0.
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- Published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 29/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Fix
- Fixed in 0.50.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
Docker Sandboxes (sbx) is affected, and an attacker who can modify a host repository's Git configuration can get a program to run on the host with the user's permissions, outside the sandbox's isolation. The issue is fixed in a later release.
Read the original description
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.
What to do
Check whether your setup matches what the bug needs.
The sandbox uses a direct mount of the host workspace, giving the agent read-write access to the host repository.Upgrade to a fixed version: 0.50.0.
Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- Docker Docker Sandboxes
From 0.31.0 · fixed in 0.50.0
Evidence 3
- Repository
- Link
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-121614
Is CVE-2026-121614 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
The bug lets Git run programs that come from the repository itself on the host. When the sandbox mounts the host workspace directly, the agent has read-write access to the host repository, so those repository-controlled programs can run outside the sandbox.Source: docs.docker.com
Which versions are affected by CVE-2026-121614?
Docker Sandboxes: from 0.31.0 before 0.50.0.Source: cve.now feed data
Am I affected, and how do I check?
Docker Sandboxes versions from 0.31.0 up to but not including 0.50.0 are listed as affected, and the issue depends on the sandbox directly mounting the host workspace. To check your setup, look up the installed Docker Sandboxes version and how the workspace is mounted into the sandbox.Source: docs.docker.com
How do I fix CVE-2026-121614?
Upgrade Docker Sandboxes to 0.50.0 or later, which is the listed fixed version.Source: docs.docker.com