CVE-2026-62862: TypeBot: Account takeover via brute-forceable 6-digit magic-link code

Published Aug 25, 2026
·
Updated

Typebot is an open-source chatbot builder. In self-hosted versions up to and including 3.17.1, the default passwordless email magic-link authentication is vulnerable to login-code brute forcing that leads to account takeover. The email provider overrides NextAuth's default cryptographically secure token with a 6-digit code generated using Math.random(), reducing the keyspace to 900,000 with a 10-minute expiry, and the code itself is the raw value placed in the magic link. The verification callback enforces no attempt limit, lockout, or CSRF protection, and an incorrect guess does not consume the real code because the adapter returns null on a not-found token, so a valid code survives unlimited guessing within its lifetime. The only rate limiter applies to the code-sending path and is keyed on the client-controlled X-Forwarded-For header, allowing an attacker to request many concurrent live codes for one victim and further raise the odds of a matching guess. As a result, an anonymous attacker who knows a victim's email address can brute-force the callback and obtain an authenticated session as that user with no victim interaction, gaining full access to the victim's bots, results, and connected integration credentials. Deployments configured for OAuth or SSO only, with no email provider, are not affected. This issue is fixed in version 3.18.0

Affected Software

2 affected components
Typebot Typebot<=3.17.1
Typebot Typebot=3.18.0

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade TypeBot to a version that resolves this vulnerability.

    Fixed in 3.18.0
  2. Compensating control

    For deployments configured for OAuth or SSO only, with no email provider, note they are not affected; ensure the deployment uses OAuth/SSO without a passwordless email provider where applicable.

Event History

Aug 25, 2026
CVE Published
via MITRE·09:43 PM
Data Sourced
via MITRE·09:43 PM
DescriptionWeakness
Data Sourced
via NVD·10:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments should be prioritized for remediation?

Self-hosted Typebot deployments up to and including version 3.17.1 that use the default passwordless email magic-link authentication should be prioritized. The issue affects that default authentication flow.

2

What must an attacker know or control to exploit this?

An attacker only needs to know the victim's email address. No account privileges or victim interaction are required.

3

Do failed login-code guesses stop further attempts or invalidate the legitimate code?

No. The verification callback has no attempt limit or lockout, and an incorrect guess does not consume the valid code. The valid code remains guessable during its 10-minute lifetime.

4

How could an attacker increase the likelihood of a successful guess?

The code-sending rate limiter is keyed to the client-controlled X-Forwarded-For header. An attacker can use this to request many concurrent live codes for a victim, increasing the chance that a guessed code matches one of them.

5

What release is referenced for updating affected deployments?

The provided references include the Typebot v3.18.0 release and the associated remediation commit. Deployments on versions through 3.17.1 are described as affected.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203