Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-wcxr-59v9-rxr8

HIGH

GHSA-wcxr-59v9-rxr8 is a high-severity (CVSS 8.4) CWE-863 vulnerability in openclaw. O3 Security confirms whether GHSA-wcxr-59v9-rxr8 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

`OpenClaw: session_status` let sandboxed subagents access parent or sibling session state

Also known asCVE-2026-32918
Published
Mar 13, 2026
Updated
Apr 1, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Blast Radius

1 pkg affected

Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.

openclawnpm
3.1Mdownloads / week

Description

Summary

The built-in session_status tool did not enforce the intended session-visibility boundary. A sandboxed subagent could supply another session's sessionKey and inspect or modify state outside its own sandbox scope.

Impact

This allowed a sandboxed child session to read parent or sibling session data and, in affected releases, update the target session's persisted model override.

Affected versions

openclaw <= 2026.3.8

Patch

Fixed in openclaw 2026.3.11 and included in later releases such as 2026.3.12. Session visibility checks now enforce the sandbox boundary before reading or mutating session state.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmopenclawall versions2026.3.11

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update openclaw to 2026.3.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wcxr-59v9-rxr8 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether GHSA-wcxr-59v9-rxr8 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-wcxr-59v9-rxr8. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary The built-in `session_status` tool did not enforce the intended session-visibility boundary. A sandboxed subagent could supply another session's `sessionKey` and inspect or modify state outside its own sandbox scope. ### Impact This allowed a sandboxed child session to read parent or sibling session data and, in affected releases, update the target session's persisted model override. ### Affected versions `openclaw` `<= 2026.3.8` ### Patch Fixed in `openclaw` `2026.3.11` and included in later releases such as `2026.3.12`. Session visibility checks now enforce the sandbox bou
O3 Security · Impact-Aware SCA

Is GHSA-wcxr-59v9-rxr8 in your dependencies?

O3 detects GHSA-wcxr-59v9-rxr8 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.