Quick answers
- Is CVE-2026-48494 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-48494 being exploited in the wild.
- How severe is CVE-2026-48494?
- Informational severity, published 11 August 2026.
- Which products and versions are affected?
- Typebot 3.16.1.
- Is there a fix for CVE-2026-48494?
- A patch was published on 2026-05-21: Version 3.17.0 includes the fix Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-48494 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-48494?
- 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 vulnerability is an authorization bypass in the WhatsApp preview webhook handler. The application authorizes the parent typebot first but then resolves the preview chat session only by a phone number identifier (wa-preview-{phone}), creating a session collision vulnerability. An authenticated attacker can mix an authorized typebotId and blockId with a foreign preview phone number from another user's preview session to inject arbitrary webhook JSON and advance draft/unpublished flows. Attack preconditions include authentication (as any user with read access to any typebot) and network access to the webhook endpoint. The patch (version 3.17.0) validates that preview sessions belong to the authorized typebot and enforce that the session is waiting on the requested webhook block.
Affected products
- TypeBot TypeBot 3.16.1
Timeline
- 2026-08-11: disclosed
- 2026-05-21: patched: Version 3.17.0 includes the fix