{"id":"CVE-2026-53813","published":"2026-06-11T20:08:11Z","modified":"2026-06-23T16:16:52Z","title":"OpenClaw < 2026.4.25 - Arbitrary Artifact Loading via Fake Package Root Resolution","vendor":"OpenClaw","product":"OpenClaw","tier":"tail","description":{"text":"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.","provenance":"source","from":"CVE.org"},"cvss":{"score":7.8,"severity":"HIGH","version":"3.1","vector":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H","provenance":"source","from":"CVE.org CNA"},"epss":{"score":0.00115,"percentile":0.01577,"provenance":"source"},"cwes":[{"id":"CWE-427","name":"Uncontrolled Search Path Element"}],"references":[{"url":"https://github.com/openclaw/openclaw/security/advisories/GHSA-v8cx-933x-r976","tags":["vendor-advisory"]},{"url":"https://www.vulncheck.com/advisories/openclaw-arbitrary-artifact-loading-via-fake-package-root-resolution","tags":["third-party-advisory"]}],"priority":{"score":5.8,"factors":[{"name":"EPSS percentile","points":0.32},{"name":"CVSS severity","points":5.46}]},"vendorSlug":"openclaw","affectedVersions":[{"vendor":"OpenClaw","product":"OpenClaw","versions":["< 2026.4.25"]}],"fixedVersions":[{"vendor":"OpenClaw","product":"OpenClaw","versions":["2026.4.25"]}],"ssvc":{"exploitation":"none","automatable":"no","technicalImpact":"total","timestamp":"2026-06-12T00:00:00+00:00","from":"CISA ADP","provenance":"source"},"affected":[{"ecosystem":"npm","package":"openclaw","vulnerableRanges":["<2026.4.25"],"patched":["2026.4.25"],"from":["GHSA-v8cx-933x-r976"],"provenance":"source"}],"summary":{"text":"OpenClaw before 2026.4.25 has a path traversal flaw in the memory-core artifact loading component, where workspace state can influence how the local package root is resolved. An attacker with access to an affected workspace, and no user interaction, can cause memory-core artifacts to be loaded from unintended local locations, potentially executing malicious code or accessing sensitive data.","provenance":"ai","model":"claude-haiku-5-5","generatedAt":"2026-11-20T22:17:12Z"},"euvd":{"id":"EUVD-2026-36319","exploited":false,"provenance":"source"}}