Skip to main content
VulnerabilityPublished Updated

CVE-2026-35625: OpenClaw · Silent privilege escalation via gateway shared-auth reconnect

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 9.4 Critical : upgrade to 2026.3.28 as a priority.

Data as of 17 Nov 2026, 20:25 UTC

CVSS 4.0 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 9% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2026.3.28
CVSS:4.0/AV:A/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Aug 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.3.28.

Affected software

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

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

AI-suggested

A patch is available and should be applied by upgrading to OpenClaw CLI version 2026.3.25 or later. The fix blocks silent reconnect scope upgrades and requires explicit pairing approval for any scope elevation. Users should update promptly to mitigate this vulnerability.

Description

OpenClaw CLI versions up to 2026.3.24 contain a vulnerability where a local shared-auth reconnect can silently escalate privileges from operator.read to operator.admin. This escalation allows a paired device to gain higher privileges without explicit user approval, potentially leading to remote code execution on the reach node. The issue is fixed in version 2026.3.25 by blocking silent reconnect scope upgrades and requiring explicit pairing approval for scope changes.

References

Community reviews

Loading reviews…