CVE-2026-32014

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

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.

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.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2026-32014 has a CVSS score of 8.0 (High). The vector is reachable from an adjacent network, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.26); upgrading removes the vulnerable code path.

Kodem intelligence

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

1. What is CVE-2026-32014? CVE-2026-32014 is a high-severity incorrect authorization vulnerability in openclaw (npm), affecting versions <= 2026.2.25. It is fixed in 2026.2.26. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2026-32014? CVE-2026-32014 has a CVSS score of 8.0 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-32014? openclaw (npm) versions <= 2026.2.25 is affected.
4. Is there a fix for CVE-2026-32014? Yes. CVE-2026-32014 is fixed in 2026.2.26. Upgrade to this version or later.
5. Is CVE-2026-32014 exploitable, and should I be worried? Whether CVE-2026-32014 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-32014 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-32014? Upgrade openclaw to 2026.2.26 or later.