Skip to main content
VulnerabilityPublished Updated

CVE-2026-35618: OpenClaw · Plivo V2 verified replay identity drifts on query-only variants

Affects openclaw-cliSource GCVE Database

0
Compare

Not known to be exploited · CVSS 8.2 High : upgrade to 2026.3.24 soon.

Data as of 16 Nov 2026, 20:25 UTC

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

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 16 Nov 2026.

What to do

Upgrade openclaw-cli to 2026.3.24.

Affected software

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

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. The issue is fixed in openclaw-cli version 2026.3.23 and later. Users should upgrade to version 2026.3.23 or newer to ensure the replay key derivation correctly excludes query parameters, preventing replay identity drift. No additional mitigation is required beyond applying the official fix.

Description

Openclaw CLI versions prior to 2026.3.23 contain a vulnerability in the Plivo V2 verification path where query-only variants of the same signed request were incorrectly treated as distinct verified requests. This occurs because the replay key was derived from the full verification URL including query parameters, allowing unsigned query changes to bypass replay identity stability. The issue was fixed in version 2026.3.23 by stabilizing the replay key derivation to exclude query parameters.

References

Community reviews

Loading reviews…