https://vulnerability.circl.lu Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 28 Sep 2026 15:32:14 +0000 https://vulnerability.circl.lu/vuln/cve-2026-32014 <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw versions prior to 2026.2.26 contain a metadata spoofing vulnerability where reconnect platform and deviceFamily fields are accepted from the client without being bound into the device-auth signature. An attacker with a paired node identity on the trusted network can spoof reconnect metadata to bypass platform-based node command policies and gain access to restricted commands.</p> <p><strong>Affected:</strong> OpenClaw</p> <p>OpenClaw versions prior to 2026.2.26 contain a metadata spoofing vulnerability where reconnect platform and deviceFamily fields are accepted from the client without being bound into the device-auth signature. An attacker with a paired node identity on the trusted network can spoof reconnect metadata to bypass platform-based node command policies and gain access to restricted commands.</p> https://vulnerability.circl.lu/vuln/cve-2026-32014 https://vulnerability.circl.lu/vuln/ghsa-r65x-2hqr-j5hf <p><strong>Affected:</strong> npm: openclaw</p> <p>## Summary</p> <p>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.</p> <p>## Affected Packages / Versions</p> <p>- Package: `openclaw` (npm) - Affected versions: `&lt;= 2026.2.25` - Latest published version at update time: `2026.2.25` - Patched version (pre-set for next release): `2026.2.26`</p> <p>## Impact</p> <p>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.</p> <p>## Fix</p> <p>- 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.</p> <p>## Fix Commit(s)</p> <p>- `7d8aeaaf06e2e616545d2c2cec7fa27f36b59b6a`</p> <p>## Release Process Note</p> <p>`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.</p> <p>OpenClaw thanks @76embiid21 for reporting.</p> <p><strong>Affected:</strong> npm: openclaw</p> <p>## Summary</p> <p>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.</p> <p>## Affected Packages / Versions</p> <p>- Package: `openclaw` (npm) - Affected versions: `&lt;= 2026.2.25` - Latest published version at update time: `2026.2.25` - Patched version (pre-set for next release): `2026.2.26`</p> <p>## Impact</p> <p>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.</p> <p>## Fix</p> <p>- 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.</p> <p>## Fix Commit(s)</p> <p>- `7d8aeaaf06e2e616545d2c2cec7fa27f36b59b6a`</p> <p>## Release Process Note</p> <p>`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.</p> <p>OpenClaw thanks @76embiid21 for reporting.</p> https://vulnerability.circl.lu/vuln/ghsa-r65x-2hqr-j5hf