CVE-2026-53813: OpenClaw: path traversal enables RCE via memory-core artifacts
HIGHOpenClaw's memory-core artifact loader trusts workspace-supplied path information without adequate validation, allowing a low-privileged attacker who controls workspace state to redirect artifact loading to an adversary-chosen local path and achieve code execution or sensitive data access (CWE-427, CVSS 7.8). Although the attack is local, AI agent deployments routinely grant workspace access to developers, automated pipelines, and third-party integrations—meaningfully widening the realistic attack surface beyond a single privileged account. Prior documented abuse of OpenClaw's ecosystem (AIID #1368, where ~17% of third-party skills were assessed as malicious and delivered credential stealers) confirms this framework is an active adversarial target, and the package's 155-CVE track record signals persistent security debt warranting elevated scrutiny. Patch to 2026.4.25 immediately; if delayed, restrict workspace write access to trusted principals only and monitor for memory-core artifact loads from paths outside the expected installation tree.
What is the risk?
High risk for organizations running OpenClaw-based AI agents. The local attack vector limits opportunistic exploitation but is realistic in multi-tenant agent platforms, shared development environments, and CI/CD pipelines where multiple principals share workspace access. Low attack complexity (AC:L) with no user interaction required (UI:N) means exploitation is straightforward once workspace access is obtained. Full CIA triad impact (C:H/I:H/A:H) combined with the framework's 155-CVE history and documented real-world ecosystem abuse elevates effective risk beyond what the 7.8 CVSS score alone suggests. The absence of EPSS data and KEV listing reduces urgency slightly, but the AIID #1368 precedent of active targeting of this framework offsets that reduction.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| OpenClaw | pip | — | No patch |
Do you use OpenClaw? You're affected.
How severe is it?
What is the attack surface?
What should I do?
6 steps-
Patch immediately: upgrade to OpenClaw 2026.4.25 or later (reference GHSA-v8cx-933x-r976).
-
Interim workaround: restrict write access to OpenClaw workspace directories to trusted service accounts only; prevent arbitrary users or integrations from modifying workspace state metadata.
-
Audit: review all workspace configurations for unexpected or recently modified package root path settings.
-
Detection: monitor file system access logs for OpenClaw processes loading artifacts from paths outside the expected installation directory tree; alert on anomalous artifact load paths.
-
Isolation: in multi-tenant deployments, enforce workspace isolation at the OS level via separate users, containers, or VMs per tenant.
-
Dependency audit: identify and patch all downstream projects that depend on OpenClaw—4 are currently tracked, but transitive dependents may be broader.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
How many AI incidents are linked? (1)
Source: AI Incident Database (AIID)
Frequently Asked Questions
What is CVE-2026-53813?
OpenClaw's memory-core artifact loader trusts workspace-supplied path information without adequate validation, allowing a low-privileged attacker who controls workspace state to redirect artifact loading to an adversary-chosen local path and achieve code execution or sensitive data access (CWE-427, CVSS 7.8). Although the attack is local, AI agent deployments routinely grant workspace access to developers, automated pipelines, and third-party integrations—meaningfully widening the realistic attack surface beyond a single privileged account. Prior documented abuse of OpenClaw's ecosystem (AIID #1368, where ~17% of third-party skills were assessed as malicious and delivered credential stealers) confirms this framework is an active adversarial target, and the package's 155-CVE track record signals persistent security debt warranting elevated scrutiny. Patch to 2026.4.25 immediately; if delayed, restrict workspace write access to trusted principals only and monitor for memory-core artifact loads from paths outside the expected installation tree.
Is CVE-2026-53813 actively exploited?
No confirmed active exploitation of CVE-2026-53813 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-53813?
1. Patch immediately: upgrade to OpenClaw 2026.4.25 or later (reference GHSA-v8cx-933x-r976). 2. Interim workaround: restrict write access to OpenClaw workspace directories to trusted service accounts only; prevent arbitrary users or integrations from modifying workspace state metadata. 3. Audit: review all workspace configurations for unexpected or recently modified package root path settings. 4. Detection: monitor file system access logs for OpenClaw processes loading artifacts from paths outside the expected installation directory tree; alert on anomalous artifact load paths. 5. Isolation: in multi-tenant deployments, enforce workspace isolation at the OS level via separate users, containers, or VMs per tenant. 6. Dependency audit: identify and patch all downstream projects that depend on OpenClaw—4 are currently tracked, but transitive dependents may be broader.
What systems are affected by CVE-2026-53813?
This vulnerability affects the following AI/ML architecture patterns: AI agent frameworks, Multi-tenant agent platforms, Agent development environments, CI/CD pipelines with AI agent components, Automated AI workflow orchestration.
What is the CVSS score for CVE-2026-53813?
CVE-2026-53813 has a CVSS v3.1 base score of 7.8 (HIGH).
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0010.001 AI Software AML.T0011.000 Unsafe AI Artifacts AML.T0037 Data from Local System AML.T0080.000 Memory AML.T0081 Modify AI Agent Configuration AML.T0112.000 Local AI Agent Compliance Controls Affected
What are the technical details?
Original Advisory
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.
Exploitation Scenario
An adversary with low-privilege access to a shared OpenClaw workspace—such as a developer account, compromised CI pipeline token, or a malicious third-party skill (as documented in AIID #1368)—modifies workspace state metadata to alter OpenClaw's local package root resolution path. On the next agent initialization or scheduled memory-core artifact reload cycle, OpenClaw follows the manipulated path and loads a malicious artifact from the attacker's controlled directory without integrity verification. The loaded artifact executes code under the agent's runtime privileges, granting the adversary access to the agent's persisted memory state, connected tool credentials, and any data the agent can reach. In a multi-tenant deployment, this lateral path escalates a single low-privilege workspace compromise into cross-tenant impact without requiring elevated OS privileges.
Weaknesses (CWE)
CVSS Vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H References
- github.com/openclaw/openclaw/security/advisories/GHSA-v8cx-933x-r976 vendor-advisory patch
- vulncheck.com/advisories/openclaw-arbitrary-artifact-loading-via-fake-package-root-resolution third-party-advisory
Timeline
Related Vulnerabilities
CVE-2026-30741 9.8 OpenClaw: RCE via request-side prompt injection
Same package: openclaw CVE-2026-28451 9.3 OpenClaw: SSRF via Feishu extension exposes internal services
Same package: openclaw GHSA-cwj3-vqpp-pmxr 8.8 openclaw: Model bypasses authz to persist unsafe config
Same package: openclaw CVE-2026-35674 8.8 OpenClaw: scope bypass enables full agent admin takeover
Same package: openclaw CVE-2026-53811 8.8 OpenClaw: privilege escalation via identity spoofing
Same package: openclaw