Which versions of OpenClaw are affected by CVE-2026-53813?

OpenClaw versions prior to 2026.4.25 contain a path traversal vulnerability enabling workspace users to execute arbitrary code or access sensitive data by manipulating package resolution paths.. A patch is available.

How to fix or mitigate CVE-2026-53813?

24 hours: Inventory all OpenClaw deployments and document current versions in use. 7 days: Upgrade to OpenClaw version 2026.4.25 or later across all environments. 30 days: Audit workspace access controls and review artifact loading logs for evidence of exploitation.

OpenClaw CVE-2026-53813

Q: What is the CVSS score of CVE-2026-53813?

CVE-2026-53813 has a CVSS 4.0 base score of 7.3 (High). CVSS vector: CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/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%.

EUVD-2026-36319 HIGH

Uncontrolled Search Path Element (CWE-427)

2026-06-11 VulnCheck

GHSA-v8cx-933x-r976

Path Traversal Information Disclosure Openclaw

7.3

CVSS 4.0 · Vendor: VulnCheck

Severity by source

Vendor (VulnCheck) PRIMARY

7.3 HIGH

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/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

7.8 HIGH

Local workspace access with a low-privileged account is required (AV:L, PR:L); manipulation is straightforward once access exists (AC:L), no extra user interaction is needed, and artifact loading yields full code execution impact (C:H/I:H/A:H).

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

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

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

CVSS:4.0/AV:L/AC:L/AT:P/PR:L/UI:N/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

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Jun 11, 2026 - 21:24 vuln.today

DescriptionCVE.org

OpenClaw before 2026.4.25 contains a path traversal vulnerability in memory-core artifact loading where workspace state influences local package root resolution. Attackers with access to affected workspaces can load memory-core artifacts from unintended local locations, potentially executing malicious code or accessing sensitive data.

AnalysisAI

Path traversal in OpenClaw before version 2026.4.25 allows attackers with workspace access to manipulate local package root resolution and load memory-core artifacts from attacker-controlled locations, leading to arbitrary code execution or sensitive data disclosure. The flaw stems from workspace state influencing artifact resolution paths (CWE-427, Uncontrolled Search Path Element). No public exploit identified at time of analysis, though VulnCheck has published a dedicated advisory describing the fake package root resolution technique.

Technical ContextAI

OpenClaw is the affected product (CPE: cpe:2.3:a:openclaw:openclaw). The root cause is CWE-427 (Uncontrolled Search Path Element): the memory-core artifact loader resolves its local package root using workspace state that an attacker can influence, rather than from a trusted, fixed location. Because artifact loading typically results in code execution within the host process, controlling the resolved path lets an attacker substitute a malicious package and have it loaded as if it were legitimate. The 'fake package root resolution' framing from VulnCheck indicates the issue is in the path/root selection logic, not in a generic '../' traversal of file reads.

RemediationAI

Vendor-released patch: upgrade OpenClaw to 2026.4.25 or later, as described in GHSA-v8cx-933x-r976 (https://github.com/openclaw/openclaw/security/advisories/GHSA-v8cx-933x-r976). Until the upgrade is applied, restrict workspace access to trusted users only and avoid opening untrusted workspaces or projects in OpenClaw, since workspace state is the input that drives the malicious package root resolution; this trades collaboration convenience for safety. Where feasible, run OpenClaw under a least-privileged OS account so that arbitrary code triggered via a malicious artifact is contained, and monitor file-system writes into OpenClaw workspace and package directories for unexpected artifact files. Consult the VulnCheck advisory (https://www.vulncheck.com/advisories/openclaw-arbitrary-artifact-loading-via-fake-package-root-resolution) for indicators specific to the fake package root resolution behavior.