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

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

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

CVE-2026-32065 presents moderate security risk rated CVSS 4.8. Exploitation could compromise the security of affected deployments. Proof-of-concept code is publicly available.. A patch is available.

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

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

How to fix or mitigate CVE-2026-32065?

Within 30 days: Identify affected systems and apply vendor patches as part of regular patch cycle. Vendor patch is available.

Openclaw CVE-2026-32065

EUVD-2026-13966 MEDIUM

Interpretation Conflict (CWE-436)

2026-03-21 VulnCheck

Authentication Bypass Openclaw

4.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

4.8 MEDIUM

AV:N/AC:H/PR:L/UI:R/S:U/C:N/I:H/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

High

Availability

None

Lifecycle Timeline

PoC Detected

Mar 24, 2026 - 21:09 vuln.today

Public exploit code

EUVD ID Assigned

Mar 21, 2026 - 01:00 euvd

EUVD-2026-13966

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

MEDIUM 4.8

DescriptionCVE.org

OpenClaw versions prior to 2026.2.25 contain an approval-integrity bypass vulnerability in system.run where rendered command text is used as approval identity while trimming argv token whitespace, but runtime execution uses raw argv. An attacker can craft a trailing-space executable token to execute a different binary than what the approver displayed, allowing unexpected command execution under the OpenClaw runtime user when they can influence command argv and reuse an approval context.

AnalysisAI

OpenClaw versions prior to 2026.2.25 contain an approval-integrity bypass vulnerability in the system.run function where the rendered command text displayed to approvers has whitespace trimmed from argv tokens, but the actual runtime execution uses the raw, untrimmed argv. An attacker with the ability to influence command arguments and reuse an approval context can craft a trailing-space executable token to execute a different binary than what was approved, resulting in arbitrary command execution under the OpenClaw runtime user. The CVSS score of 4.8 reflects the requirement for local privileges and user interaction, though the integrity impact is marked as high due to the ability to execute unauthorized commands.

Technical ContextAI

OpenClaw is a command execution framework identified via CPE cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*. The vulnerability exists in the system.run function, which implements an approval workflow where human reviewers validate commands before execution. The root cause is classified under CWE-436 (Untrusted Rendering of Prompts in a Command Execution Feature), a category addressing the mismatch between what users approve and what actually executes. The flaw occurs because the approval identity logic trims whitespace from argv tokens when rendering the command for human review, creating a normalized display, while the actual subprocess execution uses the raw argv array without trimming. This allows an attacker to inject trailing spaces into executable names (e.g., 'malicious_binary ' vs 'malicious_binary') which appear identical after trimming but execute different binaries at runtime. The vulnerability requires an attacker to have write access to influence command construction and the ability to reuse an approval context already granted by an administrator.

RemediationAI

Upgrade OpenClaw to version 2026.2.25 or later immediately. The vendor has published a fix in the commit 03e689fc89bbecbcd02876a95957ef1ad9caa176 available at https://github.com/openclaw/openclaw/commit/03e689fc89bbecbcd02876a95957ef1ad9caa176 and documented in the GitHub Security Advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-hwpq-rrpf-pgcq. Until patching is completed, restrict access to OpenClaw to trusted administrators only, audit and validate all approval workflows for commands containing trailing spaces in executable tokens, implement network segmentation to limit lateral movement from the OpenClaw runtime user account, and enforce code review processes for any command argument construction to prevent attacker-controlled whitespace injection.