Read the docs
TI-2026-84839 Aliases CVE-2026-121614GHSA-vv2q-qr3q-w59x

Docker Sandboxes host Git runs repository-controlled programs

Priority LOW 32CWE-15Published · Updated

Key facts

Attack vector
Local
Privileges required
None
User interaction
Active
Attack complexity
Low
Attack requirements
Present
Impact type
—
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

Docker Sandboxes versions 0.31.0 before 0.50.0 do not neutralize repository-controlled Git configuration when running certain host-side Git commands, which is an external control of a configuration setting (CWE-15). 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 set core.fsmonitor or another Git setting that runs an external program. Git can run that program during a later clone-mode fetch or, starting in version 0.39.0, an sbx kit push started by the user, and it runs on the host outside the sandbox's microVM isolation.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00127 2nd percentileScored 2026-11-07
Fix Fixed Docker Sandboxes (Docker): 0.50.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
DockerDocker Sandboxes0.31.0 to before 0.50.00.50.0Patch availableCNA
  • Docker Sandboxes VendorDocker Affected 0.31.0 to before 0.50.0 Fixed in 0.50.0 Patch available CNA

CPE names CNA · 1

CPEVersionsRoleVendor
cpe:2.3:a:docker:docker_sandboxes:*:*:*:*:*:*:*:*——Docker
  • cpe:2.3:a:docker:docker_sandboxes:*:*:*:*:*:*:*:* Versions — — ·Docker

Remediation

Update Docker Sandboxes to version 0.50.0 or later. The sources list no other fixed version for Docker Sandboxes.

Written with Claude Haiku 5.5 from the sources below · 2026-11-04

  • Fix · CNA Docker Sandboxes (Docker) Fixed in 0.50.0

Timeline

  1. 2026-11-03 Threatist record created from CVE-2026-121614
  2. 2026-11-04 Alias added: GHSA-vv2q-qr3q-w59x
  3. 2026-11-05 Priority changed: MEDIUM → LOW
  4. 2026-11-06 CISA SSVC decision points changed

References

Other 3

  • TI-2019-11833 Docker Desktop Community Edition before 2.1.0.1 allows local users to gain privileges by… KEVCVSS 3.1HIGH 7.8
  • TI-2019-04061 runc through 1.0-rc6, as used in Docker before 18.09.2 and other products, allows… CVSS 3.1HIGH 8.6
  • TI-2025-08316 Docker Desktop allows unauthenticated access to Docker Engine API from containers CVSS 4.0CRITICAL 9.3
  • TI-2025-02823 Elevation of Privilege in Docker Desktop for Windows during Upgrade due to Insecure Directory Deletion CVSS 4.0HIGH 7.3
  • TI-2026-14229 Tar extraction in moby/go-archive can write outside the destination directory via link following CVSS 4.0HIGH 7.1
  • TI-2023-21271 Docker Machine through 0.16.2 allows an attacker, who has control of a worker node, to… CVSS 3.1MEDIUM 6.5
See all 132 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences