Docker Sandboxes Reuses State and Configuration Directories Without Ownership Verification
Is it fixed? Not yet.
Ongoing since Nov 12, 16:19 UTC. First reported Nov 12, 16:19 UTC. Not on the vendor’s status page yet.
What happened
Docker Sandboxes reuses existing state and configuration directories without verifying ownership. If run as root with environment variables pointing to an attacker-controlled location, a local unprivileged user can substitute trusted control-plane sockets and configuration to potentially execute commands as root.
What caused it?
Docker Sandboxes reuses existing state and configuration directories without verifying their ownership, allowing an attacker-influenced environment to substitute trusted control-plane sockets and configuration when run as root.
No verified workaround yet
None of the linked reports describe a mitigation. This page updates when one appears.
Official fixTimeline
- Investigating(current)
- Workaround available(upcoming)
- Resolved(upcoming)
- First report on security advisory
Docker Sandboxes reuses existing state and configuration directories without verifying their ownership.: CVE-2026-126329 (High)
Source
Evidence
1 report · 1 CVEShow
- [1]CVE First reportDocker Sandboxes reuses existing state and configuration directories without verifying their ownership.: CVE-2026-126329 (High)(opens security advisory in a new tab)
High severity. 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…
by Tenable 0upvotes 0comments
FAQ
What happened in the Docker issue?
Docker Sandboxes reuses existing state and configuration directories without verifying ownership. If run as root with environment variables pointing to an attacker-controlled location, a local unprivileged user can substitute trusted control-plane sockets and configuration to potentially execute commands as root.
What is affected by the Docker issue?
Docker.
When did the Docker issue start and end?
It started Nov 12, 16:19 UTC and is still ongoing (6 d 12 h so far). This page updates as it develops.
How do I get alerts for Docker?
Subscribe to the Docker RSS feed for every new Docker incident, or connect an AI assistant to WhatBrokeToday over MCP and ask whether Docker is down. Docker feed
Where does this information come from?
WhatBrokeToday collects public status pages, developer community reports and security advisories, groups the ones about the same problem, and links every report under Evidence on this page. This one has 1 report from 1 independent source.