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

> Local users can substitute sockets and config in untrusted state directories to run commands as root when Docker Sandboxes runs as root.

- **Severity:** High 7.3 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Harmful if only installed:** No
- **Needs a specific call:** No
- **Fix available:** No
- **Published:** 12 Nov 2026
- **Updated:** 12 Nov 2026
- **Also known as:** GHSA-w92q-8xxw-h4r9

## What is CVE-2026-126329?

CVE-2026-126329 is a high-severity privilege escalation vulnerability in Docker Sandboxes, published on 12 Nov 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### 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.

Weakness: CWE-282 (Improper Ownership Management)

## Which versions are affected by CVE-2026-126329?

Only installations with a non-default setting turned on are exposed.


## How do I fix CVE-2026-126329?

No fix has been published for CVE-2026-126329 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-126329 being exploited?

There is no known exploitation of CVE-2026-126329 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-126329 and fix it if it is affected.

What it is: CVE-2026-126329 is a high-severity privilege escalation vulnerability in Docker Sandboxes, published on 12 Nov 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-126329 in the wild and no public exploit code.
Exposure: Only installations with a non-default setting turned on are exposed.

Affected product: Docker Sandboxes. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-126329/ (Markdown: https://insights.sbomify.com/CVE-2026-126329/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-126329
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-126329
- OSV: https://osv.dev/vulnerability/CVE-2026-126329

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-126329/
Summaries are generated and may contain mistakes; the official description above is the record.