CVE-2026-32014: OpenClaw: Node reconnect metadata spoofing could bypass platform-based node command policy
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.
Published Mar 3, 2026 · Updated Mar 20, 2026
Affected packages
openclaw
- Ecosystem
- npm
- Affected
- <= 2026.2.25
- Fixed in
- 2026.2.26
- Check
npm ls openclaw
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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
v3that signs normalizedplatformanddeviceFamily. - Verify
v3first (fallback tov2for 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.
Credited to 76embiid21.
References
- https://github.com/openclaw/openclaw/security/advisories/GHSA-r65x-2hqr-j5hf
- https://github.com/openclaw/openclaw/commit/7d8aeaaf06e2e616545d2c2cec7fa27f36b59b6a
- https://nvd.nist.gov/vuln/detail/CVE-2026-32014
- https://www.vulncheck.com/advisories/openclaw-node-reconnect-metadata-spoofing-via-unsigned-platform-fields
- https://github.com/advisories/GHSA-r65x-2hqr-j5hf
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More OpenClaw vulnerabilities
All OpenClaw entriesCVE-2026-35630
OpenClaw: QQBot native approval buttons did not enforce configured approver identity
high8.0Jul 2, 2026CVE-2026-53806
OpenClaw: Combined POSIX shell options could confuse exec revalidation
high8.8Jul 2, 2026CVE-2026-53809
OpenClaw: Embedded runner policy could be confused by provider aliases
medium3.8Jul 2, 2026CVE-2026-53810
OpenClaw's marketplace runtime extension metadata could point at unscanned payloads
high8.8Jul 2, 2026CVE-2026-53811
OpenClaw: Matrix allowFrom could bind to mutable display names
high8.8Jul 2, 2026CVE-2026-53812
OpenClaw's browser act interactions could bypass private-network navigation checks
medium7.7Jul 2, 2026
