OpenClaw: node.pair.approve missing callerScopes validation allows low-privilege operator to approve malicious nodes
Historical advisory saved 24 Oct 2026 13:17:17 UTC. The publisher may have updated it since then. Latest advisory.
osv · GHSA-2x4x-cc5g-qmmg
Published## Summary The node pairing approval path did not consistently enforce that the approving caller already held every scope requested by the node. ## Impact A lower-privileged operator could approve a pending node request for broader scopes and extend privileges onto the paired node. ## Affected Component `src/infra/node-pairing.ts, src/gateway/server-methods/nodes.ts` ## Fixed Versions - Affected: `<= 2026.3.24` - Patched: `>= 2026.3.28` - Latest stable `2026.3.28` contains the fix. ## Fix Fixed by commit `4d7cc6bb4f` (`gateway: restrict node pairing approvals`). OpenClaw thanks @AntAISecurityLab for reporting.
- Source published
- 1 Apr 2026 00:00:19 UTC
- Source modified
- 6 Apr 2026 17:46:16 UTC
- Saved here
- 24 Oct 2026 13:17:17 UTC
- Source terms
- GitHub Advisory Database · CC-BY-4.0
Original source record · Cite this exact observation · Complete original publisher JSON
Source: osv · GitHub Advisory Database · CC-BY-4.0. The publisher's wording is preserved. ChangeIntel groups the information and labels changes. The JSON record includes additional source fields.
CVSS_V3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CVSS_V4 · CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N/E:U
Publisher rating · MODERATE