CVE-2026-39969: baptisteArno typebot.io · Improper Authentication
Affects baptisteArno typebot.ioSource CVE Database V5
Not known to be exploited · CVSS 6.5 Medium : upgrade to 3.17.0 when convenient.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 3% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 3.17.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 22 May 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 30 Oct 2026.
What to do
Upgrade typebot.io and baptistearno/typebot.io to 3.17.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| baptisteArnotypebot.io | Affected
| Fixed in
|
GitHubbaptistearno/typebot.iopkg:github/baptistearno/typebot.ioOther 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
Upgrade TypeBot to version 3.17.0 or later, where this vulnerability is fixed by verifying the x-hub-signature-256 HMAC signature on incoming webhook requests. Until upgraded, be aware that webhook endpoints do not authenticate incoming requests properly, and consider restricting network access to trusted sources if possible. Patch status is not explicitly stated as 'official-fix' in the advisory, but the fix is included in version 3.17.0. No vendor advisory content was provided to override this guidance.
Description
TypeBot versions 3.16.0 and earlier have an improper authentication vulnerability in the WhatsApp Cloud API webhook endpoint. The endpoint does not verify the x-hub-signature-256 HMAC signature that Meta includes in webhook deliveries. Because the webhook URL exposes workspaceId and credentialsId in the path, which are logged and visible in multiple places, an unauthenticated attacker can send spoofed webhook messages. This can trigger bot flows, consume API resources, and interact with external services using the workspace owner's credentials. The issue is fixed in version 3.17.0.