How severe is CVE-2026-32014?

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

Which packages are affected by CVE-2026-32014?

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

How do I fix CVE-2026-32014?

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

How do I detect CVE-2026-32014 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-32014 if there is no patch (or I can't update yet)?

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.

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

No public exploit code has been indexed for CVE-2026-32014 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-32014?

CVE-2026-32014 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 9th 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-32014?

CVE-2026-32014 is classified as CWE-290 (CWE-290). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2026-32014 was published on March 19, 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-32014 — openclaw

Fix: openclaw/openclaw@7d8aeaa

CVE-2026-32014 is a CWE-290 vulnerability in openclaw. A fix is available for openclaw — see the affected versions and patch details below.

OpenClaw < 2026.2.26 - Node Reconnect Metadata Spoofing via Unsigned Platform Fields

Also known asGHSA-r65x-2hqr-j5hf

Published

Mar 19, 2026

Updated

Oct 28, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

A successful exploit gives an attacker total control of the affected component, not partial access.
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-32014.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk-0.01%

Lower risk than most CVEs9th percentile — riskier than 9% 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.

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

openclawnpm

2.5Mdownloads / week

Description

Summary

A paired node device could reconnect with spoofed platform/deviceFamily metadata and broaden node command policy eligibility because reconnect metadata was accepted from the client while these fields were not bound into the device-auth signature.

Affected Packages / Versions

Package: openclaw (npm)
Affected versions: <= 2026.2.25
Latest published version at update time: 2026.2.25
Patched version (pre-set for next release): 2026.2.26

Impact

In configurations where node command policy differs by platform, an attacker with an already paired node identity on the trusted network could spoof reconnect metadata and gain access to commands that should remain blocked for the originally paired platform.

Fix

Add device-auth payload v3 that signs normalized platform and deviceFamily.
Verify v3 first (fallback to v2 for compatibility), while pinning paired metadata server-side.
Reject reconnect metadata mismatches and require explicit repair pairing to change pinned metadata.
Add regression coverage for reconnect spoof attempts.

Fix Commit(s)

7d8aeaaf06e2e616545d2c2cec7fa27f36b59b6a

Release Process Note

patched_versions is pre-set to the planned next release 2026.2.26; once that npm release is published, the advisory can be published without further field edits.

OpenClaw thanks @76embiid21 for reporting.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`openclaw`	all versions	2026.2.26`npm install openclaw@2026.2.26`

Affected Products

1 product · 1 configurations

Application

openclawopenclaw

< 2026.2.26

range

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.26 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-32014 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.

Frequently Asked Questions

## Summary A paired node device could reconnect with spoofed `platform`/`deviceFamily` metadata and broaden node command policy eligibility because reconnect metadata was accepted from the client while these fields were not bound into the device-auth signature. ## Affected Packages / Versions - Package: `openclaw` (npm) - Affected versions: `<= 2026.2.25` - Latest published version at update time: `2026.2.25` - Patched version (pre-set for next release): `2026.2.26` ## Impact In configurations where node command policy differs by platform, an attacker with an already paired node identity

O3 Security · Impact-Aware SCA

Is CVE-2026-32014 in your dependencies?

Find it across npm, including transitive dependencies.

Scan my dependencies How O3 SCA works