Summary
OpenClaw has browser trace/download path symlink escape in temp output handling
Browser trace/download output path handling allowed symlink-root and symlink-parent escapes from the managed temp root.
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published npm version:
2026.2.24 - Affected versions:
<= 2026.2.24 - Planned patched release:
2026.2.25
Fix Commit(s)
496a76c03ba85e15ea715e5a583e498ae04d36e3
Release Process Note
patched_versions is pre-set to the release (2026.2.25) so once npm 2026.2.25 is published, the advisory is published.
OpenClaw thanks @tdjackey for reporting.
Impact
An attacker with relevant local foothold and ability to influence output paths could route writes outside the intended temp root via symlink traversal, leading to arbitrary file overwrite.
Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files. Typical impact: unauthorized file read or write outside the intended directory.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-32054? CVE-2026-32054 is a medium-severity path traversal vulnerability in openclaw (npm), affecting versions < 2026.2.25. It is fixed in 2026.2.25. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- Which versions of openclaw are affected by CVE-2026-32054? openclaw (npm) versions < 2026.2.25 is affected.
- Is there a fix for CVE-2026-32054? Yes. CVE-2026-32054 is fixed in 2026.2.25. Upgrade to this version or later.
- Is CVE-2026-32054 exploitable, and should I be worried? Whether CVE-2026-32054 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-32054 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-32054? Upgrade
openclawto 2026.2.25 or later.