Know every vulnerabilitybefore it knows you.
DevGuard continuously monitors your dependencies and alerts you when CVEs like this one affect your stack — with real-time threat intelligence built for developers.
GHSA-c37p-4qqg-3p76
No affected components available
Summary
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.
Impact
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.allowNgrokFreeTierLoopbackBypasswas 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).
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)
Fix
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.
The vulnerability can be exploited over the network without needing physical access. It is easy for an attacker to exploit this vulnerability. An attacker does not need any special privileges or access rights. No user interaction is needed for the attacker to exploit this vulnerability. The impact is confined to the system where the vulnerability exists. There is a low impact on the integrity of the data. There is a low impact on the availability of the system.
Exploitation attempts have been detected. Elevated vigilance and prompt remediation are advised.
The exploit probability is very low. The vulnerability is unlikely to be exploited in the next 30 days.
We did not find any exploit available. Neither in GitHub repositories nor in the Exploit-Database.
Browse More
Continuously monitor your dependencies and get alerted when vulnerabilities like this one affect your stack.
Checkout DevGuard