CVE-2026-29606
Webhook Signature Verification Bypass in OpenClaw Voice-Call Extension
Publication date: 2026-03-05
Last updated on: 2026-03-11
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| openclaw | openclaw | to 2026.2.14 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-306 | The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability exists in OpenClaw versions prior to 2026.2.14 and involves a webhook signature-verification bypass in the voice-call extension.
When the tunnel.allowNgrokFreeTierLoopbackBypass option is explicitly enabled, an external attacker can send forged requests to the publicly reachable webhook endpoint without needing a valid X-Twilio-Signature header.
This allows unauthorized webhook event handling and can lead to potential request flooding attacks.
How can this vulnerability impact me? :
The vulnerability allows an attacker to bypass signature verification and send unauthorized requests to the webhook endpoint.
This can result in unauthorized handling of webhook events, which may lead to security breaches or manipulation of system behavior.
Additionally, the attacker can perform request flooding attacks, potentially causing denial of service or resource exhaustion.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know