Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-62862 – Account Takeover via Brute-Forceable Email Login Codes – Typebot < 3.18.0

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-62862 is a critical authentication-bypass vulnerability in Typebot’s self-hosted passwordless email login flow, allowing an anonymous, unauthenticated attacker to take over any user account by brute-forcing the 6-digit email verification code. The flaw affects self-hosted Typebot deployments running versions prior to 3.18.0 and carries a CVSS base score of 9.1 (Critical).

Technical details

  • Root cause: Typebot generates its 6-digit login codes using Math.floor(100000 + Math.random() * 900000), a non-cryptographic PRNG that limits the keyspace to 900,000 possible values instead of using NextAuth’s cryptographically secure tokens.
  • The verification callback (GET /api/auth/callback/nodemailer) enforces no attempt limit, no lockout, and no CSRF protection, so an attacker can submit unlimited code guesses within the 10-minute validity window.
  • Failed guesses do not invalidate or consume the outstanding valid code, so the correct code remains guessable for its full lifetime.
  • The rate limiter that throttles code-sending trusts the client-controlled X-Forwarded-For header, letting an attacker rotate this header to request multiple concurrent valid codes for the same target email and improve brute-force odds.
  • Attack vector: network, no authentication or user interaction required. Impact: full account takeover, exposing the victim’s bots, results data, and integration credentials; can also be used to pre-create accounts for arbitrary email addresses.

Affected software

  • baptisteArno/typebot.io versions prior to 3.18.0 (self-hosted deployments using the email/passwordless login provider)

Severity

  • CVSS v4.0 Base Score: 9.1 (Critical)
  • Vector: CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade self-hosted Typebot instances to version 3.18.0 or later, which addresses the weak token generation, missing rate limiting, and spoofable rate-limit header issues.
  • If patching is not immediately possible: disable or restrict the passwordless email login provider, enforce strict server-side rate limiting on the /api/auth/callback/nodemailer endpoint that does not rely on client-supplied headers, and monitor authentication logs for repeated failed verification attempts against the same account.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge