cve.bz

CVE-2026-126329 Docker Sandboxes privilege escalation through untrusted state directories

7.3 highEPSS 0.1%Fix available

High (7.3) in docker docker sandboxes. EPSS 0.1% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

7.3 high
CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
EPSS
0.1% estimated probability of exploitation activity in the next 30 days; 1st percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-282 Improper Ownership Management
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
Assigned by
Docker (CNA)
NVD analysis
Awaiting analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-126329 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126329?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126329?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-126329 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-126329

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-126329](https://cve.bz/cve/badge/CVE-2026-126329.svg)](https://cve.bz/cve/CVE-2026-126329)

HTML:

<a href="https://cve.bz/cve/CVE-2026-126329"><img src="https://cve.bz/cve/badge/CVE-2026-126329.svg" alt="CVE-2026-126329"></a>

Affected

  • docker:docker sandboxes

Versions

From the CNA's record in the CVE List.

ProductAffected
Docker Sandboxesfrom 0.7.0 before 0.53.0

Fixed in

ProductFixed in
Docker Sandboxes0.53.0

Fix and patched versions

  • Docker Docker Sandboxes: fixed in 0.53.0

Attack patterns (CAPEC)

  • CAPEC-17 Using Malicious Files Likelihood: High · Severity: Very High
  • CAPEC-35 Leverage Executable Code in Non-Executable Files Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON