Open-Source Security Intelligence

Know every vulnerability
before it knows you.

DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.

Checkout DevGuardView on GitHub
Search

GHSA-ww6v-v748-x7g9

CriticalCVSS 9 / 10
Published Mar 2, 2026·Last modified Mar 25, 2026
Affected Components(0)

No affected components available

Description

Summary

In openclaw@2026.2.23, 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

Impact

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.

Remediation

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

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)

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

Risk Scores
Base Score
9.0

The vulnerability can be exploited over the network without needing physical access. It is difficult for an attacker to exploit this vulnerability and may require special conditions. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The vulnerability can affect other systems as well, not just the initial system. There is a high impact on the confidentiality of the information. There is a high impact on the integrity of the data. There is a high impact on the availability of the system.

Threat Intelligence
8.2

Exploitation activity has been observed. Apply available patches or mitigations urgently.

EPSS
0.27%

The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.

Exploit
Not available

We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.

Browse More

Critical severity
Scan your project

Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.

Checkout DevGuard