Is CVE-2026-43581 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-43581 being exploited in the wild.

How severe is CVE-2026-43581?

Critical severity, with a CVSS score of 9.6, published 6 May 2026.

Which products and versions are affected?

openclaw (npm) SEMVER:introduced=0,fixed=2026.4.10.

Is there a fix for CVE-2026-43581?

Yes. openclaw (npm): upgrade to 2026.4.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-43581 attacked?

It is attacked from the adjacent network, in a software library.

Am I affected by CVE-2026-43581?

Check whether you run openclaw (npm) or Openclaw 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.

CVE-2026-43581: OpenClaw sandbox browser CDP relay network exposure

CVE-2026-43581 · Severity: critical · CVSS 9.6 · Published 2026-05-06

OpenClaw's sandbox browser component exposes the Chrome DevTools Protocol (CDP) via a relay service that could be accessed by peer containers on the same Docker network without authentication. The CDP protocol provides complete browser control, allowing attackers to execute arbitrary JavaScript, steal cookies, or hijack navigation. This vulnerability affects deployments where OpenClaw containers run alongside untrusted or compromised peer containers on shared Docker networks.

Technologies: openclaw (npm), Openclaw. Vendors: npm, Openclaw.

Quick answers

Is CVE-2026-43581 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-43581 being exploited in the wild.
How severe is CVE-2026-43581?: Critical severity, with a CVSS score of 9.6, published 6 May 2026.
Which products and versions are affected?: openclaw (npm) SEMVER:introduced=0,fixed=2026.4.10.
Is there a fix for CVE-2026-43581?: Yes. openclaw (npm): upgrade to 2026.4.10 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-43581 attacked?: It is attacked from the adjacent network, in a software library.
Am I affected by CVE-2026-43581?: Check whether you run openclaw (npm) or Openclaw 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

openclaw (npm): upgrade to 2026.4.10 or later
```
npm install openclaw@2026.4.10
```

Technical details

The vulnerability exists in the sandbox browser CDP relay (socat) configuration, which bound to 0.0.0.0 inside the container without enforcing source-range restrictions by default. While host-side binding was already restricted to 127.0.0.1, peer containers on the same Docker bridge network could reach the relay unauthenticated. The root cause is that the CDP_SOURCE_RANGE environment variable was optional and defaulted to empty. The fix enforces mandatory source-range restriction by auto-deriving it from the Docker network gateway IP and refusing to start the socat relay without one. For bridge-style networks, the gateway IP is automatically detected; for non-bridge drivers (macvlan, ipvlan, overlay), explicit configuration is required. The patch is available in openclaw 2026.4.10 and later.

Affected products

OpenClaw openclaw < 2026.4.10

Identifiers

CVE-2026-43581
GHSA-525j-hqq2-66r4

Timeline

2026-04-17: disclosed
2026-04-10: patched: Fix merged in PR #61404; first stable release v2026.4.10

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.