Skip to main content

Openclaw CVE-2026-32046

| EUVDEUVD-2026-13941 MEDIUM
Initialization of a Resource with an Insecure Default (CWE-1188)
2026-03-21 VulnCheck GHSA-q94v-v6m9-jhq9
5.3
CVSS 3.1 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2021 - Vulnerable and Outdated Components
ASVS 5.0
V13 - Configuration Secure default settings
Impact

The CVSS 3.1 score of 5.3 (Medium severity) reflects the local attack vector (AV:L), low attack complexity (AC:L), and low privilege requirement (PR:L), indicating realistic exploitability by local users without special knowledge. The vulnerability carries moderate real-world risk: it requires local access (not network-exploitable), but the CVSS vector shows no user interaction required (UI:N) and the technical impact is confidentiality, integrity, and availability across the affected scope (C:L/I:L/A:L). The availability of vendor patches and disclosure via official GitHub security advisories suggests this is a known, prioritized issue without active mass exploitation reported. However, the absence of EPSS score and KEV status data in provided intelligence limits definitive exploitation probability assessment. For local threat models or shared systems, this warrants prompt patching; for internet-facing applications, this is lower priority relative to remote code execution vulnerabilities.

Exploit ScenarioDerived

A local user on a shared OpenClaw system identifies that the Chromium renderer sandbox is disabled due to improper configuration. They craft a malicious webpage or leverage a pre-existing renderer vulnerability (e.g., a use-after-free in the V8 engine) to achieve code execution within the renderer process. Because OS-level sandbox protections are absent, the attacker's code runs with the privileges of the OpenClaw process on the host, allowing file system access, credential theft, or lateral movement. No sandbox escape technique is required, making this a direct path from renderer exploit to host compromise.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Mar 21, 2026

OpenClaw versions prior to 2026.2.21 contain an improper sandbox configuration vulnerability (CWE-1188) that allows local attackers with low privileges to execute arbitrary code on the host system by exploiting disabled OS-level sandbox protections in the Chromium browser container. The vulnerability does not require a sandbox escape, making exploitation straightforward for local users. A patch is available from the vendor, and the issue was reported by VulnCheck with references to GitHub security advisories and patch commits.

RemediationAI

Upgrade OpenClaw to version 2026.2.21 or later immediately, following the vendor security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-43x4-g22p-3hrq. For systems that cannot be patched immediately, restrict local user access through OS-level access controls, disable local user shells where feasible, and monitor process creation events for suspicious renderer-spawned activity. Implement principle of least privilege for local accounts and consider containerizing or sandboxing OpenClaw deployments with hypervisor-level isolation to compensate for the disabled Chromium sandbox until patching is completed. Verify patch deployment by checking OpenClaw version and reviewing the referenced commit hashes.

Affected VersionsENISA

OpenClaw 0 <2026.2.21

Affected Packages

npm openclaw fix: 2026.2.21

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in npm

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability stems from improper sandbox configuration in OpenClaw, which depends on Chromium's browser container isolation mechanisms. OpenClaw (cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*) fails to enforce OS-level sandbox protections at the renderer process level, allowing attackers to exploit renderer-side vulnerabilities without needing to escape the sandbox first. This is classified as CWE-1188 (Initialization with Hard-Coded Network Resource Configuration Data), though the root cause is fundamentally a failure to enforce sandbox isolation boundaries in the Chromium renderer process. The disabled sandbox protections eliminate the intended containment layer that should prevent renderer exploits from affecting the host system.

Know when Openclaw gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

NVD PRIMARY 5.3 MEDIUM
AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector
Local
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

Lifecycle Timeline

3
PoC Detected
Mar 24, 2026 - 19:12 vuln.today
Public exploit code
Patch released
Mar 21, 2026 - 01:00 nvd
Patch available
CVE Published
Mar 21, 2026 - 00:42 nvd
MEDIUM 5.3

DescriptionCVE.org

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.

Executive ViewAI

Why It Matters

CVE-2026-32046 presents moderate security risk rated CVSS 5.3. Exploitation could compromise the security of affected deployments. Proof-of-concept code is publicly available. A patch is available and should be applied during regular vulnerability management.

Business Impact: Low
Compensating Controls

Apply vendor patch. If patching is delayed: restrict network access and enable monitoring.

Threat Intelligence Overview

EPSS Score
0.0%
Top 98% exploitable
Exploit
POC
Public exploit code exists
Data Quality
6 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
Low
Technical Impact
Partial

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy