OPENCLAW · CVE-2026-32846 · AI agents & MCP
FIX → 2026.3.28
OpenClaw's media parsing checks file paths incompletely, so a crafted media reference can point outside the app sandbox. An attacker can read files such as system files, environment files and SSH keys.
first public Mar 26, 2026 · 2 sources
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Teams running OpenClaw at version 2026.3.23 or earlier, especially where it parses media references from untrusted input. The flaw is in the media path validation (isLikelyLocalPath and isValidMedia), so deployments that never process media from outside users are less exposed. Sources do not state whether authentication is required.
Not affected if no-untrusted-media-input, version-2026.3.28-or-later
Who cares ai-agents, cwe-22, npm, openclaw
npm ls openclaw; affected versions are 2026.3.23 and earlier.openclaw package in package.json and lockfiles of any service that exposes OpenClaw media handling.Upgrade to 2026.3.28
OpenClaw through 2026.3.23 (fixed in commit 4797bbc) contains a path traversal vulnerability in media parsing that allows attackers to read arbitrary files by bypassing path validation in the isLikelyLocalPath() and isValidMedia() functions. Attackers can exploit incomplete validation and the allowBareFilename bypass to reference files outside the intended application sandbox, resulting in disclosure of sensitive information including system files, environment files, and SSH keys.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
openclaw (npm): move to 2026.3.28GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.