Summary
OpenClaw's Control UI Static File Handler Follows Symlinks and Allows Out-of-Root File Read
The Control UI static file handler previously validated asset paths lexically and then served files with APIs that follow symbolic links. A symlink placed under the Control UI root could cause out-of-root file reads.
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published version observed:
2026.2.21-2 - Affected versions:
<=2026.2.21-2 - Planned fixed release version:
2026.2.22
Technical Details
The vulnerable flow was in src/gateway/control-ui.ts, where path.join(...) + string-prefix checks were followed by file reads that resolved symlinks. This allowed directory-confinement bypasses when symlinks existed inside the Control UI root.
The fix now enforces realpath containment and verifies file identity before serving Control UI assets and SPA fallback index.html.
Fix Commit(s)
7c500ff6236fa087ec1ec88696ca9f6881e90dc5
Release Process Note
patched_versions is pre-set to the planned next release (2026.2.22). After npm release is available, publish the advisory.
OpenClaw thanks @tdjackey for reporting.
Impact
- Vulnerability type: path traversal / external file exposure via symlink following.
- Primary impact: confidentiality (out-of-root file read).
- Severity guidance: low in supported trusted-operator deployments; can be higher in unsupported shared-writable setups.
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.
CVE-2026-32020 has a CVSS score of 3.3 (Low). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.22); upgrading removes the vulnerable code path.
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-32020? CVE-2026-32020 is a low-severity path traversal vulnerability in openclaw (npm), affecting versions < 2026.2.22. It is fixed in 2026.2.22. Input manipulates file paths to reach files outside the intended directory, such as configuration or credential files.
- How severe is CVE-2026-32020? CVE-2026-32020 has a CVSS score of 3.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of openclaw are affected by CVE-2026-32020? openclaw (npm) versions < 2026.2.22 is affected.
- Is there a fix for CVE-2026-32020? Yes. CVE-2026-32020 is fixed in 2026.2.22. Upgrade to this version or later.
- Is CVE-2026-32020 exploitable, and should I be worried? Whether CVE-2026-32020 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-32020 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-32020? Upgrade
openclawto 2026.2.22 or later.