CVE-2026-39966: TypeBot: Async filter() bypasses authorization, allowing IDOR in getLinkedTypebots and leaking cross-workspace bot definitions
TypeBot is a chatbot builder tool. In versions 3.15.2, the getLinkedTypebots API endpoint returns full bot definitions to any authenticated user who references a target bot ID in a Typebot Link block, regardless of workspace ownership, leading to IDOR. The authorization check uses Array.filter() with an async callback — since filter() is synchronous, the callback always returns a truthy Promise, so the access control predicate is never actually evaluated. Any authenticated Typebot user can read the full definition of any other workspace's private bots, including: all conversation blocks and logic flow, variable values embedded in the bot (credentials, API keys, PII), webhook URLs and integration configurations. This issue has been fixed in version 3.16.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Typebotto a version that resolves this vulnerability.Fixed in 3.16.0
Event History
Frequently Asked Questions
What is the severity of CVE-2026-39966?
CVE-2026-39966 has a medium severity rating of 6.5.
How do I fix CVE-2026-39966?
To fix CVE-2026-39966, you need to update to Typebot version 3.16.0 or later.
What vulnerability does CVE-2026-39966 exploit?
CVE-2026-39966 exploits an authorization bypass in the getLinkedTypebots API, leading to insecure direct object reference (IDOR).
What can be leaked due to CVE-2026-39966?
CVE-2026-39966 can leak full bot definitions across different workspaces for any authenticated user.
Which versions of Typebot are affected by CVE-2026-39966?
CVE-2026-39966 affects Typebot version 3.15.2 and earlier.