Summary
OpenClaw: Zip extraction symlink traversal could write outside destination
A path confinement bypass in OpenClaw ZIP extraction allowed writes outside the intended destination when a pre-existing symlink was present under the extraction root.
Affected Packages / Versions
- Package:
openclaw(npm) - Latest published npm version at triage time:
2026.2.21-2 - Affected versions:
<= 2026.2.21-2 - Planned patched version for next release:
2026.2.22
Technical Details
The vulnerable path was in src/infra/archive.ts ZIP extraction logic. Output-path checks were lexical, but writes could still traverse an existing symlink in destination path segments.
The fix blocks this by:
- rejecting symlink traversal in destination path segments,
- validating resolved destination paths remain inside the extraction root,
- using no-follow file opens for ZIP output writes where supported,
- adding a regression test for pre-seeded destination symlink traversal.
Fix Commit(s)
- 4b226b74f5fd3b106a83a6347fd404172e2fd246
Release Process Note
Patched version is pre-set to the planned next release (2026.2.22).
Once npm release 2026.2.22 is published, the advisory can be published without further field edits.
OpenClaw thanks @tdjackey for reporting.
Impact
- Type: Arbitrary file write outside extraction root via symlink traversal during ZIP extraction.
- Preconditions: attacker-controlled archive extraction plus pre-existing symlink in destination 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 GHSA-JXRQ-8FM4-9P58? GHSA-JXRQ-8FM4-9P58 is a high-severity security vulnerability in openclaw (npm), affecting versions < 2026.2.22. It is fixed in 2026.2.22.
- Which versions of openclaw are affected by GHSA-JXRQ-8FM4-9P58? openclaw (npm) versions < 2026.2.22 is affected.
- Is there a fix for GHSA-JXRQ-8FM4-9P58? Yes. GHSA-JXRQ-8FM4-9P58 is fixed in 2026.2.22. Upgrade to this version or later.
- Is GHSA-JXRQ-8FM4-9P58 exploitable, and should I be worried? Whether GHSA-JXRQ-8FM4-9P58 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 GHSA-JXRQ-8FM4-9P58 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 GHSA-JXRQ-8FM4-9P58? Upgrade
openclawto 2026.2.22 or later.