Live › vulnerability › CVE-2026-121614
Docker Sandboxes versions 0.31.0 before 0.50.0 fail to neutralize Git settings stored in a repository, such as core.fsmonitor, when running certain host-side Git commands. An attacker who can edit a host repository's Git configuration can make a later fetch or sbx kit push run an external program on the host with the user's permissions, outside the sandbox isolation.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 23:15 UTC. All times on this page are UTC.
Teams that use Docker Sandboxes (sbx) with host repositories mounted read-write in direct mode, or that run sbx kit push from clone-mode sandboxes on version 0.39.0 or later. The sources say a read-only host repository mount for a clone-mode sandbox does not by itself let the sandbox alter the host Git configuration. Teams that do not use Docker Sandboxes can skip it.
No product ranges from the sources yet.
0.50.0..git/config that set core.fsmonitor or other external-program Git settings.Unknown from the sources.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-121614")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.