CVE
Docker Sandboxes root privilege escalation via unverified state directories
- Exploited
- No known exploitation
- Fix
- Fixed in 0.53.0
- Who is exposed
- Specific setups only
Do first: Upgrade to a fixed version: 0.53.0.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- FIRST's estimate of the chance attackers exploit it in the next 30 days, updated daily.What do these mean? →
- 0.10% · 0th percentile
- 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
- 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 reuses existing state and configuration directories without verifying their ownership. If sbx or sandboxd is run as root with HOME or, on Linux, XDG_STATE_HOME pointing to an attacker-controlled location, a local unprivileged user can substitute control-plane sockets and configuration trusted by the root process, potentially executing commands as root. Exploitation requires a privileged invocation with an attacker-influenced environment. The issue affects Linux and macOS and is fixed in version 0.53.0.
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure5/25Specific setups only
- Reach17/20Affects Docker (a widely deployed server, runtime, framework or database)
- Severity7.3/10CVSS 7.3
- 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
What to do
Upgrade to a fixed version: 0.53.0.
Workaround: Avoid running sbx or sandboxd as root. If a privileged invocation is required, use HOME and XDG_STATE_HOME values belonging to the target account and ensure its state and configuration directories are not controlled by another user.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-126329 (Docker Sandboxes privilege escalation through untrusted state directories), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-126329 (entry last updated 2026-11-12):
Affected:
- Docker Docker Sandboxes: from 0.7.0, fixed in 0.53.0
Fixed versions: 0.53.0.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: local access, low-privilege login, no user action.
Workaround: Avoid running sbx or sandboxd as root. If a privileged invocation is required, use HOME and XDG_STATE_HOME values belonging to the target account and ensure its state and configuration directories are not controlled by another user. (source: https://www.cve.org/CVERecord?id=CVE-2026-126329)
CISA KEV: CVE-2026-126329 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126329 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://docs.docker.com/ai/sandboxes/
- https://www.cve.org/CVERecord?id=CVE-2026-126329
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-126329
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126329"}.Timeline
- CVE published
- First seen by cve.now
- Posted on X by cve.now
Affected versions
- Docker Docker Sandboxes
From 0.7.0 · fixed in 0.53.0
Evidence 3
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-126329
Is CVE-2026-126329 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
Which versions are affected by CVE-2026-126329?
Docker Sandboxes: from 0.7.0 before 0.53.0.Source: cve.now feed data
How do I fix CVE-2026-126329?
Upgrade Docker Sandboxes to version 0.53.0 or later. Until then, avoid running sbx or sandboxd as root; if a privileged invocation is required, use HOME and XDG_STATE_HOME values belonging to the target account and make sure its state and configuration directories are not controlled by another user.Source: cve.org