Is there a patch available for EUVD-2026-25344?

Yes, a patch is available for EUVD-2026-25344. Update the affected software to the latest version immediately.

OpenClaw EUVD-2026-25344

Q: What is the CVSS score of EUVD-2026-25344?

EUVD-2026-25344 has a CVSS 4.0 base score of 5.4 (Medium). CVSS vector: CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

| CVE-2026-41360 MEDIUM

Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367)

2026-04-23 VulnCheck

GHSA-v3p7-858r-pr8m

Information Disclosure Openclaw

5.4

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

5.4 MEDIUM

CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

6.7 MEDIUM

Local filesystem write access and script-replacement timing require AV:L and AC:H; some system presence needed (PR:L); operator must complete approval (UI:R); no scope change (S:U).

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

4.0 AV:L/AC:H/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from NVD.

CVSS VectorNVD

Attack Vector

Local

Attack Complexity

High

Privileges Required

Low

User Interaction

Scope

Lifecycle Timeline

Source Code Evidence Fetched

Jul 24, 2026 - 03:18 vuln.today

Analysis Generated

Jul 24, 2026 - 03:18 vuln.today

CVSS changed

Apr 23, 2026 - 22:28 NVD

6.7 (MEDIUM) 5.4 (MEDIUM)

EUVD ID Assigned

Apr 23, 2026 - 22:15 euvd

EUVD-2026-25344

Patch released

Apr 23, 2026 - 22:15 nvd

Patch available

CVE Published

Apr 23, 2026 - 21:58 nvd

MEDIUM 5.4

Blast Radius

ecosystem impact

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

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

Ecosystem-wide dependent count for version 2026.4.2.

DescriptionCVE.org

OpenClaw before 2026.4.2 contains an approval integrity vulnerability in pnpm dlx that fails to bind local script operands consistently with pnpm exec flows. Attackers can replace approved local scripts before execution without invalidating the approval plan, allowing execution of modified script contents.

AnalysisAI

Approval integrity bypass in OpenClaw's pnpm dlx command-planning path (all versions up to 2026.4.1) allows a low-privileged local attacker to replace an approved local script between the approval decision and actual execution, running arbitrary code under a still-valid approval plan. The root cause is a TOCTOU flaw (CWE-367): unlike the parallel pnpm exec flow, pnpm dlx did not bind local script operands into the approval plan's mutable-file tracking, leaving the script file unmonitored after approval. No active exploitation is confirmed (EPSS 0.01%, SSVC exploitation: none), though SSVC rates technical impact as total given full C/I/A exposure on the vulnerable system.

Technical ContextAI

OpenClaw (npm package, CPE: cpe:2.3:a:openclaw:openclaw) provides an AI coding-agent harness that integrates with pnpm's dlx and exec subcommands via a node-host command-planning and approval pipeline. CWE-367 (Time-of-check Time-of-use race condition) describes the root cause precisely: during approval planning, pnpm dlx invocations did not resolve and bind local script operands (e.g., ./run.ts) into the plan's mutableFileOperand field, while the pnpm exec path correctly tracked these via revalidateApprovedMutableFileOperand. This asymmetry left a window between operator approval and script execution in which a co-located attacker could overwrite the script file without invalidating the approval. The fix commit 176c059b05357df1bc09d4328a2380670859eeff routes pnpm dlx through the same mutable-script binding logic used by pnpm exec, closing the TOCTOU window.

RemediationAI

Upgrade OpenClaw to version 2026.4.2 or later, which binds pnpm dlx local script operands through the approval planner's mutable-script tracking path before any approval is granted, closing the TOCTOU window. The fix is documented in GitHub Security Advisory GHSA-w6wx-jq6j-6mcj (https://github.com/openclaw/openclaw/security/advisories/GHSA-w6wx-jq6j-6mcj) and implemented in commit 176c059b05357df1bc09d4328a2380670859eeff (https://github.com/openclaw/openclaw/commit/176c059b05357df1bc09d4328a2380670859eeff). If immediate upgrade is not possible, restrict local filesystem write access for all accounts that share the environment with OpenClaw operators, reducing an attacker's ability to modify script files between approval and execution - though this imposes operational constraints on shared-user environments. As an additional workaround, avoid invoking local-path scripts (e.g., ./run.ts) through OpenClaw's pnpm dlx approval flow until patched; this eliminates the vulnerable code path at the cost of restricting scripted workflows that rely on this invocation pattern.