# CVE-2026-90562: LangBot before 4.10.11 Authentication Bypass via Weak Recovery Key

> Remote attackers can brute-force weak password recovery keys to reset the administrator password and gain unauthorized access to the LangBot platform.

- **Severity:** Critical 9.2 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-6h2j-ghfm-664v

## What is CVE-2026-90562?

CVE-2026-90562 is a critical authentication bypass vulnerability in langbot-app LangBot, published on 13 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

LangBot before 4.10.11 generates password recovery keys with only 24 bits of entropy and applies no rate limiting to the unauthenticated reset-password endpoint. Remote attackers knowing the administrator email can exhaust the keyspace through concurrent requests to reset the admin password and gain account access.

Weakness: CWE-331 (Insufficient Entropy)

## Which versions are affected by CVE-2026-90562?


## How do I fix CVE-2026-90562?

No fix has been published for CVE-2026-90562 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-90562 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-90562 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-90562 and fix it if it is affected.

What it is: CVE-2026-90562 is a critical authentication bypass vulnerability in langbot-app LangBot, published on 13 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-90562 exists.

Affected product: langbot-app LangBot. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-90562/ (Markdown: https://insights.sbomify.com/CVE-2026-90562/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-90562
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-90562
- OSV: https://osv.dev/vulnerability/CVE-2026-90562

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-90562/
Summaries are generated and may contain mistakes; the official description above is the record.