CVE-2026-22171 is a path traversal in OpenClaw, scored 8.2 (High). The Feishu media download builds temporary file paths from untrusted media keys, so a crafted key can write files outside the temp directory. Versions before 2026.2.19 are affected, and 2026.2.19 or later fixes it, so update the npm package.
What's affected
- Product: OpenClaw, npm package openclaw
- Affected: versions up to 2026.2.17 per the GitHub advisory, described in NVD as prior to 2026.2.19
- Fixed: 2026.2.19 and later
- Component: the Feishu extension, in extensions/feishu/src/media.ts
- Impact: arbitrary file write within the permissions of the OpenClaw process
- Status: not in the CISA Known Exploited Vulnerabilities catalog
If you do not use the Feishu extension, the vulnerable code path is not part of your setup, but updating is still the simplest way to be sure.
How to check if you're exposed
Check the installed version in each project and in global installs:
npm ls openclaw
npm ls -g openclaw
Anything below 2026.2.19 should be updated. Also check whether the Feishu integration is enabled in your configuration, since that is where the vulnerable media download lives.
Then look at the process. The risk follows the permissions of the user that runs OpenClaw. A process running as a service account with write access to application code or scripts has far more to lose than one confined to a container.
What to do now
- Update the openclaw package to 2026.2.19 or later everywhere it is installed.
- Rebuild container images that bundle OpenClaw and redeploy them.
- Run OpenClaw as an unprivileged user with write access only to the folders it needs.
- If you use the Feishu integration, review recently written files outside the temp directory.
- Add a check to CI that fails when openclaw resolves to a version below the fixed one.
Why it matters
The Feishu media flow receives keys that identify an image or a file. The advisory says those keys, imageKey and fileKey, were placed directly into temporary file names. If a key contains traversal segments such as parent directory references, the resulting path points outside the temp directory, and the write lands wherever the process is allowed to write. The class is CWE-22, path traversal.
An attacker needs to control the media key values that come back to the client. The record describes this as writing arbitrary files within the process permissions. What that means in practice depends on the host: overwriting a configuration file or a script that runs later can turn a file write into code execution.
The fix is the standard one for this class: do not build paths from untrusted strings. Generate file names yourself, or strip the key to a safe character set before using it.
Dependency updates are the most reliable way to close flaws like this, so make the version check automatic.
Try it yourself
Click through it at your own pace, or open it full screen.
Quick check
Is the Feishu extension on by default?
The sources we checked do not say. Check your own configuration, and update regardless, as the fix is a simple version bump.
Which versions are fixed?
Version 2026.2.19 and later. The advisory lists 2026.2.17 and earlier as affected.
Sources
Last reviewed: 19 October 2026.
