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

Back
New CVE Detected

CVE-2026-90562 – Authentication Bypass via Weak Recovery Key – LangBot 4.0.8.1 through 4.10.10

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-90562 is an authentication bypass vulnerability in LangBot, an open-source LLM-powered chatbot platform, caused by insufficient entropy in its password recovery mechanism (CWE-331). Versions before 4.10.11 generate password reset keys with only 24 bits of entropy and enforce no effective rate limiting on the unauthenticated reset-password endpoint, allowing a remote attacker who knows an administrator’s email address to brute-force the recovery key and take over the admin account. The issue carries a CVSS v4.0 base score of 9.2 (Critical).

Technical details

  • Root cause: The recovery secret is generated with secrets.token_hex(3), producing only 24 bits of entropy — a keyspace of 16,777,216 possible values — for a credential that grants full administrative access.
  • Missing anti-automation controls: The unauthenticated POST /api/v1/user/reset-password endpoint’s only protective measure is a 3-second asyncio.sleep() delay in the request handler, which suspends only the current coroutine and does not serialize or block concurrent requests.
  • Trigger conditions: An attacker needs only the target administrator’s email address; no prior authentication, session, or user interaction is required.
  • Attack vector: Network-based. By issuing large numbers of concurrent requests to the reset-password endpoint, an attacker can exhaust the entire 24-bit keyspace in a matter of hours (estimated ~333 guesses/second with 1,000 concurrent requests, exhausting the keyspace in roughly 7 hours on average) since there is no per-IP or per-account rate limiting, lockout, or exponential backoff.
  • Impact: Successful exploitation resets the administrator’s password, granting the attacker full administrative control over the LangBot instance and its connected integrations/data.

Affected software

  • LangBot versions 4.0.8.1 through 4.10.10 (inclusive)
  • Fixed in version 4.10.11

Severity

  • CVSS v4.0: 9.2 (Critical) — CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
  • CVSS v3.1: 8.1 (High) — CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade LangBot to version 4.10.11 or later, which increases recovery key entropy and adds rate limiting to the reset-password flow.
  • If immediate patching is not possible:
    • Restrict network exposure of the LangBot admin panel and API to trusted networks or a VPN.
    • Front the reset-password endpoint with an external WAF or reverse-proxy rule that enforces strict per-IP and per-account rate limiting.
    • Monitor for abnormal volumes of requests to the reset-password endpoint and alert on spikes.
    • Rotate administrator credentials and review admin account activity for signs of unauthorized password resets.

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