GHSA-2x4x-cc5g-qmmg
CRITICALGHSA-2x4x-cc5g-qmmg is a critical-severity (CVSS 9.8) CWE-863 vulnerability in openclaw. O3 Security confirms whether GHSA-2x4x-cc5g-qmmg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
OpenClaw: node.pair.approve missing callerScopes validation allows low-privilege operator to approve malicious nodes
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
openclawnpmDescription
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.28contains the fix.
Fix
Fixed by commit 4d7cc6bb4f (gateway: restrict node pairing approvals).
OpenClaw thanks @AntAISecurityLab for reporting.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | openclaw | all versions | 2026.3.28 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for openclaw. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update openclaw to 2026.3.28 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2x4x-cc5g-qmmg 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.
How O3 protects you
O3 pinpoints whether GHSA-2x4x-cc5g-qmmg is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-2x4x-cc5g-qmmg. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-2x4x-cc5g-qmmg in your dependencies?
O3 detects GHSA-2x4x-cc5g-qmmg across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.