Quick answers
- Is CVE-2026-39967 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-39967 being exploited in the wild.
- How severe is CVE-2026-39967?
- Low severity, with a CVSS score of 3.1, published 22 May 2026.
- Which products and versions are affected?
- Typebot <= 3.15.2.
- Is there a fix for CVE-2026-39967?
- A patch was published on 2026-04-08: Version 3.16.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-39967 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-39967?
- 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
A missing authorization check in the `findResult` Prisma query allows for cross-tenant data access. The query retrieves chat results based solely on a `resultId` without verifying that the result belongs to the specific `typebotId` being accessed. An attacker can exploit this by providing a foreign `resultId` to the `startChat` endpoint. Successful exploitation requires the target chatbot to have the `rememberUser` setting enabled and requires the attacker to know or guess a valid 24-character CUID2 identifier. If these conditions are met, the attacker can retrieve previous user answers, session variables, and PII. The issue is fixed in version 3.16.0 by enforcing a `typebotId` filter in the database query.
Affected products
- baptisteArno TypeBot <= 3.15.2
Timeline
- 2026-04-08: patched: Version 3.16.0 released
- 2026-05-22: disclosed: Security advisory published
- 2026-05-22: advisory: CVE-2026-39967 assigned