Skip to main content
CVE-2026-42426VulnerabilityPublished Updated

Openclaw cli: OpenClaw `node.pair.approve` placed

Affects openclaw-cliSource GCVE Database

0
Compare
Authoritative record:CVE-2026-42426· High 8.7

Not known to be exploited · CVSS 8.7 High : upgrade to 2026.4.8 soon.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulnCheck)CVSS 4.08.7
CNA (VulnCheck)CVSS 3.18.8
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.4.8
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 Apr 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.4.8.

Affected software

ProductAffectedFixed in
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threatsAffected
  • >=2026.1.29 <2026.4.8
Fixed in
  • 2026.4.8

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade to openclaw version 2026.4.8 or later, which contains the official fix correcting the permission scope for node.pair.approve. The fix has been verified with targeted regression tests. No additional mitigation is required once patched.

Description

OpenClaw CLI versions up to 2026.4.7 contain a vulnerability where the node.pair.approve method is incorrectly scoped to operator.write instead of the more restrictive operator.pairing scope. This misconfiguration allows unprivileged users with operator.write permissions to approve pairings, potentially leading to unauthorized control over exec-capable nodes. The issue affects local user-controlled assistants and does not assume multi-tenant environments. A fix is available in version 2026.4.8.

References

Community reviews

Loading reviews…