What is the CVSS score of CVE-2026-32058?

CVE-2026-32058 has a CVSS 3.1 base score of 2.6 (Low). CVSS vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N. EPSS exploitation probability: 0.0%.

Which versions of Openclaw are affected by CVE-2026-32058?

CVE-2026-32058 is a low-severity vulnerability (CVSS 2.6). The limited severity suggests constrained impact, typically requiring specific conditions or local access for exploitation.. A patch is available.

Is there a public PoC exploit available for CVE-2026-32058?

Yes, a public proof-of-concept exploit is available for CVE-2026-32058. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-32058?

During next maintenance window: Apply vendor patches when convenient. Vendor patch is available.

Openclaw CVE-2026-32058

EUVD-2026-13962 LOW

Incorrect Authorization (CWE-863)

2026-03-21 VulnCheck

Authentication Bypass Openclaw

2.6

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

2.6 LOW

AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:L/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

High

Privileges Required

Low

User Interaction

Required

Scope

Unchanged

Confidentiality

None

Integrity

Low

Availability

None

Lifecycle Timeline

PoC Detected

Mar 24, 2026 - 21:10 vuln.today

Public exploit code

EUVD ID Assigned

Mar 21, 2026 - 01:00 euvd

EUVD-2026-13962

Analysis Generated

Mar 21, 2026 - 01:00 vuln.today

Patch released

Mar 21, 2026 - 01:00 nvd

Patch available

CVE Published

Mar 21, 2026 - 00:42 nvd

LOW 2.6

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

2 npm packages depend on openclaw (2 direct, 0 indirect)

Ecosystem-wide dependent count for version 2026.2.26.

DescriptionCVE.org

OpenClaw versions prior to 2026.2.26 contain an approval context-binding weakness in system.run execution flows with host=node that allows reuse of previously approved requests with modified environment variables. Attackers with access to an approval id can exploit this by reusing an approval with changed env input, bypassing execution-integrity controls in approval-enabled workflows.

AnalysisAI

OpenClaw versions prior to 2026.2.26 contain an approval context-binding weakness that allows attackers to reuse previously approved system.run execution requests with modified environment variables, bypassing approval-enabled workflow integrity controls. An attacker with access to an approval ID can exploit this vulnerability to execute commands with different environment settings than originally approved, effectively circumventing execution-integrity safeguards. The vulnerability requires local/network access and user interaction, resulting in a low CVSS score of 2.6, but represents a meaningful integrity violation in approval workflows where execution consistency is critical.

Technical ContextAI

The vulnerability exists in OpenClaw's approval and request handling mechanism for system.run execution flows when host=node is specified. Root cause is classified under CWE-863 (Incorrect Authorization), specifically a context-binding weakness where the approval system fails to maintain integrity binding between the approval decision and the actual execution context. The vulnerability allows modification of environment variables (env input) after approval has been granted but before execution occurs, breaking the semantic contract that approved requests execute exactly as approved. This affects OpenClaw (CPE: cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*), which is an orchestration/workflow platform where approval workflows are security-critical components for compliance and operational control.

RemediationAI

Upgrade OpenClaw to version 2026.2.26 or later to apply the patch. The vendor has released a fix available at commit 10481097f8e6dd0346db9be0b5f27570e1bdfcfa (see https://github.com/openclaw/openclaw/commit/10481097f8e6dd0346db9be0b5f27570e1bdfcfa). Until patching is completed, implement additional controls by restricting approval ID access to trusted administrators, implementing audit logging for all approval-reuse attempts, enforcing environment variable immutability after approval grant, and requiring re-approval for any requests with modified execution context. In approval-critical workflows, add a secondary verification step that compares the approved request signature against the actual execution parameters before system.run invocation.