openclaw
Affected
- introduced
0, fixed2026.3.23(semver)
Fixed versions
2026.3.23
Fix
- Fixed version
2026.3.23npm install [email protected]
Advisory
Also known as: CVE-2026-35618
OpenClaw: Plivo V2 verified replay identity drifts on query-only variants
Summary
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
openclaw (npm)< 2026.3.23>= 2026.3.23v2026.3.23-2 (630f1479c44f78484dfa21bb407cbe6f171dac87)2026.3.23-2Root 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 keysRelease 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.ts now derives the V2 replay key with createPlivoV2ReplayKey(...), which hashes getBaseUrlNoQuery(url) plus the nonce.extensions/voice-call/src/webhook-security.test.ts contains the regression test treats query-only V2 variants as the same verified request.Thanks @smaeljaish771 for reporting.
High Basis: The source's own band: HIGH
0, fixed 2026.3.23 (semver)2026.3.23
2026.3.23npm install [email protected]Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0