Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-v892-hwpg-jwqp

MEDIUMFix: openclaw/openclaw@3aa94af

GHSA-v892-hwpg-jwqp is a medium-severity (CVSS 6.1) Path Traversal vulnerability in openclaw. O3 Security confirms whether GHSA-v892-hwpg-jwqp is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

OpenClaw vulnerable to path traversal (Zip Slip) in archive extraction during explicit installation commands

Also known asCVE-2026-28486
Published
Mar 2, 2026
Updated
Mar 6, 2026
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed

Real-World Exposure

1 pkg affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.

openclawnpm
3.2Mdownloads / week

Description

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

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
📦npmopenclaw2026.1.16-2&&< 2026.2.142026.2.14

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. 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.

  3. 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.

  4. How O3 protects you

    O3 pinpoints whether GHSA-v892-hwpg-jwqp is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

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

## 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) - `op
O3 Security · Impact-Aware SCA

Is GHSA-v892-hwpg-jwqp in your dependencies?

O3 detects GHSA-v892-hwpg-jwqp across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.