CVE-2026-121614: Docker Sandboxes host Git executes repository-controlled programs
Noroxi assessment
Priority: Monitor (action score 28/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.12% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No special conditions are required; it is repeatable.
- Fixed version: Docker Docker Sandboxes 0.50.0.
Low priority for now. Upgrade to Docker Docker Sandboxes 0.50.0 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Nov 3, 2026
- Updated
- Nov 6, 2026
- EPSS
- 0.1% · 2th percentile
- CWE
- CWE-15
Report tools
Action score
28
Low priority for now.
- CVSS
- 28 / 40 · 7.1 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.1%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · Docker
- 7.1
- NVD has not scored this yet; the score shown is the CNA’s.
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
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Docker). Independent of NVD's CPE analysis and usually ahead of it.
Docker Docker Sandboxes
- 0.31.0 and later · before 0.50.0affected · semver
Same product
docker: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-77179Docker Sandboxes guest can write arbitrary macOS host files via a symlink in the virtio-fs stored-path fallback37Monitor
- CVE-2026-79994Docker Sandboxes UDS forwarder can reach arbitrary host Unix sockets through a symlink race34Monitor
- CVE-2026-103916Docker Sandboxes sbx cp follows workspace symlinks outside the authorized host directory33Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-105452Oct 8, 2026 · Docker Sandboxes egress proxy could forward unrecognized client credentials to managed hosts23Monitor
- ← EarlierCVE-2026-105570Oct 8, 2026 · Docker Sandboxes OAuth response masking could be bypassed with a case-variant token host26Monitor
- Later →CVE-2026-126329Nov 12, 2026 · Docker Sandboxes privilege escalation through untrusted state directories29Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Docker Docker Sandboxes | 0.50.0 | Vendor (CNA) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
- Published
- Fix recordedsame day
- TodayNov 14, 2026+10 d
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Nitesh Surana (niteshsurana.com)TrendAI Researchfinder
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Not on record for this CVE: patch commit or PR link · variant or chain candidate.
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- A
- Scope
- X
Weakness class (CWE)
CWE-15 · External Control of System or Configuration SettingCVSS vector
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-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Subverting Environment Variable ValuesCAPEC-13likelihood: High · Very High
- XML Schema PoisoningCAPEC-146likelihood: Low · High
- Configuration/Environment ManipulationCAPEC-176Medium
- Manipulate Registry InformationCAPEC-203Medium
- Modification of Registry Run KeysCAPEC-270likelihood: Medium · Medium
- Schema PoisoningCAPEC-271likelihood: Low · High
- Replace Winlogon Helper DLLCAPEC-579
- Target Programs with Elevated PrivilegesCAPEC-69likelihood: High · Very High
ATT&CK techniques
- Modify RegistryT1112
- Boot or Logon Autostart Execution: Registry Run Keys / Start FolderT1547.001
- Boot or Logon Autostart Execution: Winlogon helper DLLT1547.004
- Boot or Logon Autostart Execution: ActiveT1547.014
- Impair Defenses:Impair Command History LoggingT1562.003
- Hijack Execution Flow:Dynamic Linker HijackingT1574.006
- Hijack Execution Flow:Path Interception by PATH Environment VariableT1574.007
- Plist ModificationT1647
Change log
- SSVC exploitation— → none
- Exploit maturity— → none
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Show all references (2 more)Show less
Vendor advisories and official records. Exploit/PoC links are deliberately left out.