OpenclawApplication

CVE-2026-32915

HIGH · 8.8 CVSS v3.1 Published 2026-03-29
Fix available
A fix is available. Upgrade to 2026.3.11 or later.
See remediation →
90/100
Remediation priority · Urgent
Zero-click

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 · unedited
OpenClaw before 2026.3.11 contains a sandbox boundary bypass vulnerability allowing leaf subagents to access the subagents control surface and resolve against parent requester scope instead of their own session tree. A low-privilege sandboxed leaf worker can steer or kill sibling runs and cause execution with broader tool policies by exploiting insufficient authorization checks on subagent control requests.

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 confidence

OpenClaw before 2026.3.11 has a sandbox boundary bypass where leaf subagents can access the subagent control surface and resolve against parent requester scope instead of their own session tree. This allows low-privilege sandboxed leaf workers to kill or hijack sibling runs and execute with broader tool policies due to insufficient authorization checks on subagent control requests.

MitigationUpdate to OpenClaw version 2026.3.11 or later, which contains proper authorization enforcement on subagent control surfaces to prevent cross-session sandbox escapes.

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
OpenclawApplication
Affected:< 2026.3.11

CVSS 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
High

CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed OpenClaw version
    Run 'openclaw --version' command or inspect the installed package metadata to determine the exact version number
    Affected if Version is below 2026.3.11
  2. Verify subagent or leaf worker usage
    Review OpenClaw configuration files and active process definitions for subagent, leaf worker, or nested agent configurations
    Affected if Subagent or leaf worker features are enabled or configured in the environment
  3. Inspect subagent control authorization settings
    Examine OpenClaw configuration for authorization controls on subagent control surfaces, particularly settings governing cross-session operations or parent scope resolution
    Affected if Authorization enforcement is missing, disabled, or configured to allow parent requester scope resolution for leaf subagents

Environment is affected if running OpenClaw below version 2026.3.11 with subagent or leaf worker functionality active and missing proper authorization checks on subagent control surfaces.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2026.3.11 or later
Fixed in 2026.3.11
Interim mitigation

Update to OpenClaw version 2026.3.11 or later, which contains proper authorization enforcement on subagent control surfaces to prevent cross-session sandbox escapes.

Recommended fix Moderate confidence

2026.3.11

  1. 1. Backup your current OpenClaw configuration and data
  2. 2. Consult the official OpenClaw release notes for 2026.3.11 to understand any migration requirements
  3. 3. Stop the OpenClaw service or daemon
  4. 4. Upgrade OpenClaw to version 2026.3.11 or later using your package manager or build system
  5. 5. Verify the upgrade by checking the installed version matches or exceeds 2026.3.11
  6. 6. Restart the OpenClaw service
  7. 7. Test that subagent sandboxing functions correctly with limited-privilege workers

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Openclaw Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
40.0 hours of engineering $6,920
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $11,072.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32915 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32915 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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