dbcve.org
OpenclawApplication

CVE-2026-32046

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-21
Fix available
A fix is available. Upgrade to 2026.2.21 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 versions prior to 2026.2.21 contain an improper sandbox configuration vulnerability that allows attackers to execute arbitrary code by exploiting renderer-side vulnerabilities without requiring a sandbox escape. Attackers can leverage the disabled OS-level sandbox protections in the Chromium browser container to achieve code execution on the host system.

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 versions before 2026.2.21 have improper sandbox configuration that disables OS-level sandbox protections in its embedded Chromium browser container. Attackers can exploit renderer-side vulnerabilities to achieve arbitrary code execution on the host system without needing to escape a sandbox.

MitigationUpdate OpenClaw to version 2026.2.21 or later, which contains proper sandbox configuration. Verify that OS-level Chromium sandbox protections are enabled and functioning.

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.2.21

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 OpenClaw installed version
    Locate the OpenClaw installation and query its version using the application's about dialog, --version command-line flag, or installed package metadata
    Affected if The installed version is earlier than 2026.2.21
  2. Identify embedded Chromium component
    Inspect the OpenClaw installation directory for bundled Chromium browser files or a chromium subdirectory
    Affected if OpenClaw bundles an embedded Chromium browser component
  3. Examine Chromium launch configuration
    Review configuration files, startup scripts, or command-line arguments passed to the embedded Chromium to determine if sandbox-related flags such as --no-sandbox or --disable-sandbox are present
    Affected if Sandbox-disabling flags are present in the launch configuration
  4. Verify runtime sandbox initialization
    Check application logs, debug output, or system call traces for messages indicating whether the Chromium sandbox was successfully enabled at runtime
    Affected if The sandbox was not initialized or failed to initialize during browser use

The environment is affected if OpenClaw version is below 2026.2.21 and the embedded Chromium sandbox is explicitly disabled or fails to initialize.

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.2.21 or later
Fixed in 2026.2.21
Vendor patch github.com →
Interim mitigation

Update OpenClaw to version 2026.2.21 or later, which contains proper sandbox configuration. Verify that OS-level Chromium sandbox protections are enabled and functioning.

Recommended fix High confidence

OpenClaw 2026.2.21 or later

  1. 1. Verify current OpenClaw version by checking the application or running 'openclaw --version'
  2. 2. Back up all existing configurations, user data, and any custom settings
  3. 3. Download OpenClaw version 2026.2.21 or later from the official GitHub releases page
  4. 4. Install the new version using the standard installation process for your platform
  5. 5. Verify the installation completed successfully and confirm the new version is running
  6. 6. Review application logs after startup to ensure no startup errors related to sandbox configuration

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

Fix this in Openclaw Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32046 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-32046 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