Openclaw cli: OpenClaw Twilio voice-call webhook auth bypass when ngrok loopback compatibility is enabled
Affects openclaw-cliSource GCVE Database
Not known to be exploited · CVSS 6.5 Medium : upgrade to 2026.2.14 when convenient.
Data as of 17 Nov 2026, 20:25 UTC
- EPSS
- 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 2026.2.14
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 13 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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.2.14.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Homebrewopenclaw-clipkg:brew/openclaw-cliOther threats | Affected
| Fixed in
|
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 in openclaw version 2026.2.14 that removes the signature verification bypass while maintaining trusted forwarded header support. Users should upgrade to version 2026.2.14 or later. If upgrading immediately is not possible, ensure that the voice-call extension is disabled or that the 'tunnel.allowNgrokFreeTierLoopbackBypass' option is not enabled. Avoid exposing the webhook endpoint publicly without proper signature verification.
Description
A signature verification bypass vulnerability exists in the OpenClaw CLI's Twilio voice-call webhook extension when the ngrok free-tier loopback compatibility option is enabled. This optional voice-call extension is disabled by default, and the bypass only occurs if the specific configuration option 'tunnel.allowNgrokFreeTierLoopbackBypass' is explicitly enabled. Exploitation requires the webhook endpoint to be publicly reachable, typically via a public ngrok URL used during development. An attacker could send forged webhook requests without a valid Twilio signature, potentially causing unauthorized webhook event handling and request flooding. The issue affects OpenClaw CLI versions from 2026.1.29 up to but not including 2026.2.14. A fix is available in version 2026.2.14, which removes the signature verification bypass while preserving trusted forwarded headers for correct signature validation.
References
- github.com/openclaw/openclaw/security/advisories/GHSA-c37p-4qqg-3p76 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-29606 (opens in a new tab)
- github.com/openclaw/openclaw/commit/ff11d8793b90c52f8d84dae3fbb99307da51b5c9 (opens in a new tab)
- github.com/openclaw/openclaw (opens in a new tab)
- github.com/openclaw/openclaw/releases/tag/v2026.2.14 (opens in a new tab)
- vulncheck.com/advisories/openclaw-webhook-signature-verification-bypass-via-ngrok-loopback-compatibility (opens in a new tab)