CVE-2026-32038

In [email protected], sandbox network hardening blocks network=host but still allows network=container:<id>.

This can let a sandbox join another container's network namespace and reach services available in that namespace.

Preconditions and Trust Model Context

This issue requires a trusted-operator configuration path (for example setting agents.defaults.sandbox.docker.network in gateway config). It is not an unauthenticated remote exploit by itself.

Details

Current validation blocks only host, while forwarding other values to Docker create args:

• validateNetworkMode(network) only rejects values in BLOCKED_NETWORK_MODES = {"host"}.
• buildSandboxCreateArgs(...) validates then forwards cfg.network into --network.
• Browser sandbox helper also treats container: as an accepted mode in network preparation.

Effective behavior:

• host -> blocked
• container:<id> -> accepted and forwarded

Patch Status

Fixed on main in commit 14b6eea6e:
https://github.com/openclaw/openclaw/commit/14b6eea6e

Follow-up refactor/cleanup (no policy rollback):
https://github.com/openclaw/openclaw/commit/5552f9073

Publication Update (2026-02-25)

[email protected] is published on npm and contains the fix commit(s) listed above. This advisory now marks >= 2026.2.24 as patched.

Type: sandbox network isolation hardening bypass.

Practical impact depends on deployment:

• Requires ability to influence trusted sandbox network config.
• Higher impact when a target container exposes privileged/internal network reachability.

CVE-2026-32038 has a CVSS score of 9.0 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.24); upgrading removes the vulnerable code path.

Kodem intelligence

Block namespace-join style network modes (including container:<id>) for sandbox containers, and keep strict allowlisting for safe network modes.

1. What is CVE-2026-32038? CVE-2026-32038 is a medium-severity security vulnerability in openclaw (npm), affecting versions <= 2026.2.23. It is fixed in 2026.2.24.
2. How severe is CVE-2026-32038? CVE-2026-32038 has a CVSS score of 9.0 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-32038? openclaw (npm) versions <= 2026.2.23 is affected.
4. Is there a fix for CVE-2026-32038? Yes. CVE-2026-32038 is fixed in 2026.2.24. Upgrade to this version or later.
5. Is CVE-2026-32038 exploitable, and should I be worried? Whether CVE-2026-32038 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-32038 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-32038? Upgrade openclaw to 2026.2.24 or later.