Quick answers
- Is CVE-2026-39969 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39969 being exploited in the wild.
- How severe is CVE-2026-39969?
- Medium severity, with a CVSS score of 6.5, published 22 May 2026.
- Which products and versions are affected?
- Typebot <= 3.16.1.
- Is there a fix for CVE-2026-39969?
- A patch was published on 2026-05-21: Version 3.17.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-39969 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-39969?
- Check whether you run Typebot at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The WhatsApp Cloud API webhook endpoint (POST /v1/workspaces/{workspaceId}/whatsapp/{credentialsId}/webhook) in TypeBot versions 3.16.1 and prior fails to validate the 'x-hub-signature-256' HMAC signature provided by Meta. Because the endpoint is defined as a public procedure without authentication, an attacker who knows or discovers the workspaceId and credentialsId (which are often exposed in web server logs or Meta's dashboard) can send crafted JSON payloads. This allows for the injection of spoofed messages into bot flows, potentially leading to unauthorized consumption of integrated services (like OpenAI) and pollution of the results database. The vulnerability was addressed in version 3.17.0 by implementing proper signature verification.
Affected products
- baptisteArno typebot.io <= 3.16.1
Timeline
- 2026-05-21: patched: Version 3.17.0 released
- 2026-05-22: disclosed: Security advisory published