Summary
OpenClaw: Plivo V2 verified replay identity drifts on query-only variants
Before v2026.3.23, the Plivo V2 verification path treated query-only variants of the same signed request as fresh verified work. Plivo V2 signatures authenticate baseUrl + nonce, but the replay key was derived from the full verification URL including the query string, so unsigned query-only changes minted a new verifiedRequestKey.
Affected Packages / Versions
- Package:
openclaw(npm) - Affected:
< 2026.3.23 - Fixed:
>= 2026.3.23 - Latest released tag checked:
v2026.3.23-2(630f1479c44f78484dfa21bb407cbe6f171dac87) - Latest published npm version checked:
2026.3.23-2
Root Cause
The vulnerable logic lived in extensions/voice-call/src/webhook-security.ts. V2 signature validation already canonicalized to the base URL without query parameters, but the replay key used the full verificationUrl, letting query-only variants bypass replay identity stability.
Fix Commit(s)
b0ce53a79cf63834660270513e26d921899b4e5b,fix(voice-call): stabilize plivo v2 replay keys
Release Status
The fix commit is contained in released tags v2026.3.23 and v2026.3.23-2. The latest shipped tag and npm release both include the fix.
Code-Level Confirmation
extensions/voice-call/src/webhook-security.tsnow derives the V2 replay key withcreatePlivoV2ReplayKey(...), which hashesgetBaseUrlNoQuery(url)plus the nonce.extensions/voice-call/src/webhook-security.test.tscontains the regression testtreats query-only V2 variants as the same verified request.
Thanks @smaeljaish771 for reporting.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-35618? CVE-2026-35618 is a high-severity security vulnerability in openclaw (npm), affecting versions < 2026.3.23. It is fixed in 2026.3.23.
- Which versions of openclaw are affected by CVE-2026-35618? openclaw (npm) versions < 2026.3.23 is affected.
- Is there a fix for CVE-2026-35618? Yes. CVE-2026-35618 is fixed in 2026.3.23. Upgrade to this version or later.
- Is CVE-2026-35618 exploitable, and should I be worried? Whether CVE-2026-35618 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-35618 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-35618? Upgrade
openclawto 2026.3.23 or later.