Quick answers
- Is CVE-2026-126329 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-126329 being exploited in the wild.
- How severe is CVE-2026-126329?
- Informational severity, published 12 November 2026.
- Which products and versions are affected?
- Docker Sandboxes prior to 0.53.0.
- Is there a fix for CVE-2026-126329?
- Yes: fixed in 0.53.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-126329 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-126329?
- Check whether you run Docker Sandboxes at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 0.53.0
Technical details
The vulnerability exists in how Docker Sandboxes handles state and configuration directories: it reuses existing directories without verifying ownership, creating a time-of-check-to-time-of-use (TOCTOU) race condition. A local attacker can substitute malicious control-plane sockets in directories where sbx or sandboxd expect trusted configuration, gaining root code execution when the privileged process loads these files. This affects Linux and macOS platforms and requires the privilege escalation vector of a root-level invocation with attacker-influenced environment variables.
Affected products
- Docker Sandboxes prior to 0.53.0
Timeline
- 2026-11-12: disclosed
- 2026-11-12: patched