GHSA-v892-hwpg-jwqp is a medium-severity (CVSS 6.1) Path Traversal vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.
OpenClaw vulnerable to path traversal (Zip Slip) in archive extraction during explicit installation commands
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-v892-hwpg-jwqp.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-v892-hwpg-jwqp plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 377,636 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
openclawnpmDescription
Summary
A path traversal (Zip Slip) issue in archive extraction during explicit installation commands could allow a crafted archive to write files outside the intended extraction directory.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected versions:
>=2026.1.16-2 <2026.2.14 - Fixed version:
2026.2.14
Affected Commands / Flows
This only affects users who run installation commands against an untrusted archive (local file or download URL), for example:
openclaw skills install(download+extract installers)openclaw hooks install(archive installs)openclaw plugins install(archive installs)openclaw signal install(signal-cli asset extraction)
It is not triggered by receiving messages or normal gateway operation.
Impact
Arbitrary file write as the current user. In the worst case this can be used for persistence or code execution if an attacker can convince a user to install a crafted archive.
Fix
- Fix commit:
3aa94afcfd12104c683c9cad81faf434d0dadf87 - Released in:
2026.2.14
Credits
OpenClaw thanks @markmusson for reporting.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | ≥ 2026.1.16-2&&< 2026.2.14 | 2026.2.14npm install openclaw@2026.2.14 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update openclaw to 2026.2.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-v892-hwpg-jwqp is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-v892-hwpg-jwqp can be triaged on real exposure rather than presence alone.
Tailored to GHSA-v892-hwpg-jwqp. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-v892-hwpg-jwqp in your dependencies?
O3 Security finds GHSA-v892-hwpg-jwqp across npm dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.