# CVE-2026-121614: Docker Sandboxes host Git executes repository-controlled programs


- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 3 Nov 2026
- **Updated:** 6 Nov 2026
- **Also known as:** GHSA-vv2q-qr3q-w59x

## What is CVE-2026-121614?

CVE-2026-121614 is a high-severity vulnerability in Docker Sandboxes, published on 3 Nov 2026. 

### Official 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.

Weakness: CWE-15 (External Control of System or Configuration Setting)

## Which versions are affected by CVE-2026-121614?


## How do I fix CVE-2026-121614?

No fix has been published for CVE-2026-121614 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-121614 being exploited?

There is no known exploitation of CVE-2026-121614 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-121614 and fix it if it is affected.

What it is: CVE-2026-121614 is a high-severity vulnerability in Docker Sandboxes, published on 3 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-121614 in the wild and no public exploit code.

Affected product: Docker Sandboxes. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-121614/ (Markdown: https://insights.sbomify.com/CVE-2026-121614/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-121614
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-121614
- OSV: https://osv.dev/vulnerability/CVE-2026-121614

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-121614/
Summaries are generated and may contain mistakes; the official description above is the record.
