CVE-2026-32918
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedOpenClaw before 2026.3.11 contains a session sandbox escape vulnerability in the session_status tool that allows sandboxed subagents to access parent or sibling session state. Attackers can supply arbitrary sessionKey values to read or modify session data outside their sandbox scope, including persisted model overrides.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOpenClaw before 2026.3.11 has a session sandbox escape vulnerability in the session_status tool. Sandboxed subagents can supply arbitrary sessionKey values to bypass sandbox isolation and access or modify parent or sibling session state, including persisted model overrides.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2026.3.11CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check OpenClaw versionLocate the OpenClaw installation and retrieve its version number using the tool's version command or by inspecting the package/library versionAffected if The installed version is lower than 2026.3.11 (e.g., 2026.3.10, 2026.2.x, etc.)
-
Verify session_status tool availabilityDetermine whether the session_status tool is exposed to or accessible by sandboxed subagents in your deploymentAffected if The session_status tool is accessible to sandboxed subagents and can accept sessionKey parameters
-
Inspect sandbox isolation configurationReview the sandbox configuration to see if it restricts subagents from supplying arbitrary sessionKey values to the session_status toolAffected if The sandbox permits subagents to pass custom sessionKey values to session_status without validation or restriction
-
Check for session state access patternsMonitor or review logs for any instances where subagents accessed parent or sibling session state using the session_status toolAffected if Sandboxed subagents have successfully accessed or modified sessions other than their own
You are affected if running any OpenClaw version before 2026.3.11 and the session_status tool is accessible to sandboxed subagents without proper sessionKey validation.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2026.3.11
Upgrade to OpenClaw version 2026.3.11 or later, which contains the fix for the session sandbox escape in the session_status tool.
2026.3.11
- 1. Identify all OpenClaw instances running in your environment
- 2. Check the currently installed version of OpenClaw (typically via CLI command like 'openclaw --version' or checking package metadata)
- 3. Upgrade OpenClaw to version 2026.3.11 or later
- 4. After upgrade, verify the session_status tool no longer accepts arbitrary sessionKey values from sandboxed subagents
- 5. Confirm that sandboxed subagents can only access their own session state
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32918 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32918 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data