CVE-2026-29606

A Twilio webhook signature-verification bypass in the voice-call extension could allow unauthenticated webhook requests when a specific ngrok free-tier compatibility option is enabled.

Affected Packages / Versions

• Package: openclaw (npm)
• Affected versions: <= 2026.2.13 (latest published as of 2026-02-14)
• Patched versions: >= 2026.2.14 (planned next release; pending publish)

This issue is limited to configurations that explicitly enable and expose the voice-call webhook endpoint.

Not affected by default:

• The voice-call extension is optional and disabled by default.
• The bypass only applied when tunnel.allowNgrokFreeTierLoopbackBypass was explicitly enabled.
• Exploitation required the webhook to be reachable (typically via a public ngrok URL during development).

Worst case (when exposed and the option was enabled):

• An external attacker could send forged requests to the publicly reachable webhook endpoint that would be accepted without a valid X-Twilio-Signature.
• This could result in unauthorized webhook event handling (integrity) and request flooding (availability).

A critical operation is accessible without requiring any authentication. Typical impact: any user can invoke the privileged function.

CVE-2026-29606 has a CVSS score of 6.5 (Medium). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (2026.2.14); upgrading removes the vulnerable code path.

Kodem intelligence

allowNgrokFreeTierLoopbackBypass no longer bypasses signature verification. It only enables trusting forwarded headers on loopback so the public ngrok URL can be reconstructed for correct signature validation.

Fix commit(s):

• ff11d8793b90c52f8d84dae3fbb99307da51b5c9

Thanks @p80n-sec for reporting.

1. What is CVE-2026-29606? CVE-2026-29606 is a medium-severity missing authentication for critical function vulnerability in openclaw (npm), affecting versions < 2026.2.14. It is fixed in 2026.2.14. A critical operation is accessible without requiring any authentication.
2. How severe is CVE-2026-29606? CVE-2026-29606 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of openclaw are affected by CVE-2026-29606? openclaw (npm) versions < 2026.2.14 is affected.
4. Is there a fix for CVE-2026-29606? Yes. CVE-2026-29606 is fixed in 2026.2.14. Upgrade to this version or later.
5. Is CVE-2026-29606 exploitable, and should I be worried? Whether CVE-2026-29606 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
6. What actually determines whether CVE-2026-29606 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.
7. How do I fix CVE-2026-29606? Upgrade openclaw to 2026.2.14 or later.