Docker Sandboxes: Improper Ownership Management
CVE-2026-126329 is a high-severity improper ownership management vulnerability in Docker Sandboxes from Docker, with a CVSS 4.0 base score of 7.3 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists version 0.53.0 as the first without the flaw, so updating Docker Sandboxes to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.1% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Docker Sandboxes to 0.53.0 or a later version.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Docker | Docker Sandboxes | 0.7.0 up to, but not including, 0.53.0 | 0.53.0 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Attack requirements
- PresentThe target must be in a specific state or configuration for the attack to work.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Confidentiality (vulnerable system)
- HighSerious loss of confidentiality on the vulnerable system.
- Integrity (vulnerable system)
- HighSerious loss of integrity on the vulnerable system.
- Availability (vulnerable system)
- HighSerious loss of availability on the vulnerable system.
- Confidentiality (other systems)
- NoneNo loss of confidentiality on systems beyond the vulnerable one.
- Integrity (other systems)
- NoneNo loss of integrity on systems beyond the vulnerable one.
- Availability (other systems)
- NoneNo loss of availability on systems beyond the vulnerable one.
Vector: 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/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. Scored by CNA (docker.com).
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Ownership Management
The product assigns the wrong ownership, or does not properly verify the ownership, of an object or resource.
How developers prevent this class of flaw
- Very carefully manage the setting, management, and handling of privileges. Explicitly manage trust zones in the software.
More Improper Ownership Management vulnerabilities (CWE-282)
Timeline
- CVE record published.
References
Other references
Other vulnerabilities in Docker Sandboxes
- 7.1 High severity
- 8.4 High severity
- 8.7 High severity
- 9.4 Critical severity
- 7.1 High severity
Recent Improper Ownership Management vulnerabilities
- 8.8 High severity
- 8.0 High severity
- 7.8 High severity
- 8.8 High severity
- 7.8 High severity
- 9.1 Critical severity
Spotted an error? Tell us.