Summary
OpenClaw vulnerable to path traversal in Feishu media temp-file naming allows writes outside os.tmpdir()
OpenClaw’s Feishu media download flow used untrusted Feishu media keys (imageKey / fileKey) when building temporary file paths in extensions/feishu/src/media.ts.
Because those keys were interpolated directly into temp-file paths, traversal segments could escape the temp directory and redirect writes outside os.tmpdir().
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published npm version at triage:
2026.2.17 - Affected versions:
<= 2026.2.17 - Fixed version:
2026.2.19
Fix Commit(s)
c821099157a9767d4df208c6b12f214946507871cdb00fe2428000e7a08f9b7848784a0049176705ec232a9e2dff60f0e3d7e827a7c868db5254473f
Impact
This is an arbitrary file write issue (within the OpenClaw process file permissions).
If an attacker can control Feishu media key values returned to the client (for example via compromised upstream response path), they can influence where downloaded bytes are written.
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
The fix removes key-derived temp-file naming and keeps downloads in safe temp locations. Additional hardening isolates SDK writeFile calls in per-download temp directories (mkdtemp) with deterministic cleanup, enforces Feishu key trust-boundary validation, and adds a repository guard test against dynamic path.join(os.tmpdir(), \...${...}`)` patterns in runtime code.
OpenClaw thanks @allsmog for reporting.
Frequently Asked Questions
- What is CVE-2026-22171? CVE-2026-22171 is a medium-severity path traversal vulnerability in openclaw (npm), affecting versions < 2026.2.19. It is fixed in 2026.2.19. 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-22171? openclaw (npm) versions < 2026.2.19 is affected.
- Is there a fix for CVE-2026-22171? Yes. CVE-2026-22171 is fixed in 2026.2.19. Upgrade to this version or later.
- Is CVE-2026-22171 exploitable, and should I be worried? Whether CVE-2026-22171 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-22171 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-22171? Upgrade
openclawto 2026.2.19 or later.