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

CVE-2026-32910 has a CVSS 3.1 base score of 7.3 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H.

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

OpenClaw versions before 2026.3.1 contain an approval bypass vulnerability that allows attackers with local access to execute unauthorized binaries despite operator approval controls, circumventing a…. A patch is available.

How to fix or mitigate CVE-2026-32910?

Within 24 hours: inventory all OpenClaw deployments and document current versions. Within 7 days: upgrade all OpenClaw instances to version 2026.3.1 or later and validate approval mechanisms function correctly post-upgrade. Within 30 days: conduct audit of execution logs to identify any suspicious binary execution patterns, and implement filesystem write restrictions on directories in system PATH where unprivileged users have write access.

Openclaw CVE-2026-32910

EUVD-2026-14593 HIGH

Untrusted Search Path (CWE-426)

2026-03-23 VulnCheck

GHSA-cp5x-5627-vxqx

Authentication Bypass Openclaw

7.3

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

7.3 HIGH

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Updated

Apr 16, 2026 - 06:18 EUVD-patch-fix

executive_summary

Re-analysis Queued

Apr 16, 2026 - 05:29 backfill_euvd_patch

patch_released

Patch available

Apr 16, 2026 - 05:29 EUVD

2026.3.1

EUVD ID Assigned

Mar 23, 2026 - 22:00 euvd

EUVD-2026-14593

Analysis Generated

Mar 23, 2026 - 22:00 vuln.today

CVE Published

Mar 23, 2026 - 21:36 nvd

HIGH 7.3

DescriptionCVE.org

OpenClaw before 2026.3.1 contains an approval bypass vulnerability in system.run where non-path-like argv[0] tokens fail to bind executable identity, allowing post-approval executable rebind. Attackers can modify PATH resolution after approval to execute a different binary than the operator approved.

AnalysisAI

OpenClaw versions prior to 2026.3.1 contain an approval bypass vulnerability in the system.run function that allows attackers to execute a different binary than the one approved by an operator. The vulnerability stems from non-path-like argv[0] tokens failing to bind to executable identity, enabling post-approval PATH manipulation to redirect execution to attacker-controlled binaries. With a CVSS score of 7.3 and requiring local access with low privileges and user interaction, this represents a significant privilege escalation and integrity bypass risk in environments using OpenClaw's execution approval mechanisms.

Technical ContextAI

The affected product is OpenClaw (cpe:2.3:a:openclaw:openclaw:*:*:*:*:*:*:*:*), a software application with a system.run approval mechanism intended to control executable invocation. This vulnerability is classified as CWE-426 (Untrusted Search Path), where the root cause lies in the failure to properly bind executable identity when argv[0] contains non-path-like tokens (such as bare command names without directory components). When system.run approves an execution based on argv[0] that lacks path information, it relies on PATH environment variable resolution to locate the actual binary. Because the executable identity is not bound at approval time, an attacker can manipulate the PATH variable after approval but before execution, causing a different binary with the same name to be invoked instead of the approved one. This breaks the security guarantee of the approval mechanism, as the approved token becomes a reference to whatever executable happens to be found first in the modified PATH.

RemediationAI

Upgrade OpenClaw to version 2026.3.1 or later, which addresses the approval bypass vulnerability by properly binding executable identity regardless of argv[0] format. The patch details and upgrade instructions are available in the GitHub security advisory at https://github.com/openclaw/openclaw/security/advisories/GHSA-q399-23r3-hfx4. Until patching is completed, organizations should implement compensating controls including requiring all system.run approvals to use absolute paths rather than bare command names, restricting write access to directories in the PATH environment variable for users who can trigger approval requests, and auditing all system.run invocations to detect PATH manipulation attempts. In high-security environments, consider temporarily disabling system.run functionality or requiring additional verification that the resolved executable matches the intended approved binary before execution proceeds.