How severe is CVE-2026-28486?

No CVSS score has been assigned to CVE-2026-28486 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2026-28486?

CVE-2026-28486 affects the following packages: openclaw (npm). Ecosystems affected: npm.

How do I fix CVE-2026-28486?

Update openclaw to 2026.2.14 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-28486 is resolved across your whole dependency graph.

How do I detect CVE-2026-28486 in my npm dependencies?

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.

How do I mitigate CVE-2026-28486 if there is no patch (or I can't update yet)?

Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

Is CVE-2026-28486 actively exploited in the wild?

No public exploit code has been indexed for CVE-2026-28486 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2026-28486?

CVE-2026-28486 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 7th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2026-28486?

CVE-2026-28486 is classified as Path Traversal (CWE-22). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was CVE-2026-28486 published, and has it been updated?

CVE-2026-28486 was published on March 5, 2026 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦 npm

Not in CISA KEV

CVE-2026-28486 — openclaw

Fix: openclaw/openclaw@3aa94af

CVE-2026-28486 is a Path Traversal vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw 2026.1.16-2 < 2026.2.14 - Path Traversal (Zip Slip) in Archive Extraction via Installation Commands

Also known asGHSA-v892-hwpg-jwqp

Published

Mar 5, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Nov 2, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 CVE-2026-28486.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs7th percentile — riskier than 7% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

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.

132other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

openclawnpm

2.4Mdownloads / 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

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	≥ 2026.1.16-2&&< 2026.2.14	2026.2.14`npm install openclaw@2026.2.14`

Affected Products

1 product · 2 configurations

Application

openclawopenclaw

≥ 2026.1.20 && < 2026.2.14

1 version

2026.1.16-2

Detection & mitigation playbook

Open-source dependency

Detect
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 CVE-2026-28486 is resolved across your whole dependency graph.
Workarounds
Resolve every user-supplied path to its canonical form and reject anything that escapes the intended directory, and run the component under an account that has no read or write access outside the directory it legitimately serves.

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 CVE-2026-28486 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works