CVE-2026-90562

HIGHPre-NVD 8.18.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

Score 8.1 from GitHub Security Advisory (severity: CRITICAL) published 2026-09-13. The CNA's CVSS baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: the CNA's CVSS, EPSS, GitHub Security Advisory
Trending — 3 sources updated this weekElevated

Also known asEUVD-2026-76987 (ENISA EUVD) · GHSA-6h2j-ghfm-664v (GitHub Security Advisories)Source: ENISA EUVD

8.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
CISA-KEV: Not listedEPSS PROB: 0.7%CVSS: 8.1Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
52
EG Risk 52/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity81% × 45%
Impact severity (EG Severity): CVSS 8.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.7%
EPSS %ILE
54th
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (8.1): severity, escalated by confirmed exploitation. This CVE's 8.1 is its impact severity (EG Severity), not escalated.

EG Severity
8.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
0.7% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-27). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

September 13, 2026

Last Modified

September 24, 2026

Advisory Details (6)

Auto-updated Sep 13, 2026
Patch available. Sources: github_commit.
Web page

LangBot before 4.10.11 Authentication Bypass via Weak Recovery Key | Advisories | VulnCheck

https://www.vulncheck.com/advisories/langbot-before-4.10.11-authentication-bypass-via-weak-recovery-key
GitHub commit Patch Available

commit 267232c24f93 (langbot-app/LangBot)

Patch available: langbot-app/LangBot v4.10.11 (contains commit 267232c24f93)

https://github.com/langbot-app/LangBot/commit/267232c24f93c515d6fd3f7f81c0676066ab1ab8
Web page

LangBot/src/langbot/pkg/api/http/controller/groups/user.py at v4.10.2 · langbot-app/LangBot · GitHub

https://github.com/langbot-app/LangBot/blob/v4.10.2/src/langbot/pkg/api/http/controller/groups/user.py
Web page

LangBot/src/langbot/pkg/core/stages/genkeys.py at v4.10.2 · langbot-app/LangBot · GitHub

https://github.com/langbot-app/LangBot/blob/v4.10.2/src/langbot/pkg/core/stages/genkeys.py
Web page

GitHub - langbot-app/LangBot: Production-grade platform for building agentic IM bots - 生产级多平台智能机器人开发平台/ Agent、知识库编排、插件系统 / Bots for Discord / Slack / LINE / Telegram / WeChat(企业微信, 企微智能机器人, 公众号) / 飞书 / 钉钉 / QQ / Matrix e.g. Integrated with ChatGPT(GPT), DeepSeek, Dify, n8n, Langflow, Coze, Claude, Gemini, GLM, Ollama, SiliconFlow, Moonshot, openclaw / hermes agent, deerflow · GitHub

https://github.com/langbot-app/LangBot
Web page

Unauthenticated admin account takeover via low-entropy (24-bit) recovery key and missing brute-force protection · Issue #2392 · langbot-app/LangBot · GitHub

https://github.com/langbot-app/LangBot/issues/2392

Vendor Advisories for CVE-2026-90562(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 67× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 99 of 147 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 1 repeat row among the latest 100 is merged into the row it repeats. The 48 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:36 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  2. 2026-10-31 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  3. 2026-10-30 16:35 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  4. 2026-10-29 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  5. 2026-10-28 16:33 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  6. 2026-10-27 18:36 UTCEG score recompute
  7. 2026-10-27 18:36 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  8. 2026-10-27 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  9. 2026-10-26 16:32 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  10. 2026-10-25 16:34 UTCEPSS rescoreEPSS 0.7% · 54th percentile
  11. 2026-10-25 13:51 UTCEG score recompute
  12. 2026-10-24 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  13. 2026-10-23 16:32 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  14. 2026-10-22 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  15. 2026-10-21 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  16. 2026-10-20 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  17. 2026-10-20 07:07 UTCEG score recompute
  18. 2026-10-20 07:07 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  19. 2026-10-19 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  20. 2026-10-18 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  21. 2026-10-18 03:01 UTCEG score recompute
  22. 2026-10-17 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  23. 2026-10-16 16:45 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  24. 2026-10-15 16:33 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  25. 2026-10-14 16:34 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
Show 74 more
  1. 2026-10-13 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  2. 2026-10-13 12:33 UTCEG score recompute
  3. 2026-10-13 12:33 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  4. 2026-10-13 04:45 UTCEG score recompute
  5. 2026-10-13 04:45 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  6. 2026-10-12 16:35 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  7. 2026-10-12 14:46 UTCEG score recompute
  8. 2026-10-11 19:52 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  9. 2026-10-11 19:14 UTCEG score recompute
  10. 2026-10-11 16:30 UTCEG score recompute
  11. 2026-10-11 13:50 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  12. 2026-10-11 13:45 UTCEG score recompute
  13. 2026-10-11 06:39 UTCEG score recompute
  14. 2026-10-11 06:39 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  15. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  16. 2026-10-10 17:16 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  17. 2026-10-10 04:52 UTCEG score recompute
  18. 2026-10-10 04:52 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  19. 2026-10-09 20:08 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  20. 2026-10-09 16:19 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  21. 2026-10-08 23:07 UTCEG score recompute
  22. 2026-10-08 23:07 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  23. 2026-10-08 17:14 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  24. 2026-10-08 08:03 UTCEG score recompute
  25. 2026-10-08 08:03 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  26. 2026-10-07 23:48 UTCEPSS rescoreEPSS 0.7% · 53rd percentile
  27. 2026-10-07 19:37 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  28. 2026-10-07 07:11 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  29. 2026-10-06 18:49 UTCEG score recompute
  30. 2026-10-06 18:49 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  31. 2026-10-06 15:18 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  32. 2026-10-06 06:28 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  33. 2026-10-05 18:05 UTCEG score recompute
  34. 2026-10-05 18:05 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  35. 2026-10-05 17:44 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  36. 2026-10-05 05:44 UTCEG score recompute
  37. 2026-10-05 05:44 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  38. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  39. 2026-10-04 17:21 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  40. 2026-10-04 04:48 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  41. 2026-10-03 16:27 UTCEG score recompute
  42. 2026-10-03 16:27 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  43. 2026-10-03 04:06 UTCEG score recompute
  44. 2026-10-03 04:06 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  45. 2026-10-02 15:44 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  46. 2026-10-02 03:23 UTCEG score recompute
  47. 2026-10-02 03:23 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  48. 2026-10-01 19:51 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  49. 2026-10-01 14:39 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  50. 2026-10-01 02:18 UTCEG score recompute
  51. 2026-10-01 02:18 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  52. 2026-09-30 15:04 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  53. 2026-09-30 13:57 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  54. 2026-09-30 01:35 UTCEG score recompute
  55. 2026-09-30 01:35 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  56. 2026-09-29 06:57 UTCEG score recompute
  57. 2026-09-29 06:57 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  58. 2026-09-28 18:35 UTCEG score recompute
  59. 2026-09-28 18:35 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  60. 2026-09-28 13:52 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  61. 2026-09-28 05:55 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  62. 2026-09-27 17:34 UTCEG score recompute
  63. 2026-09-27 17:33 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  64. 2026-09-27 13:49 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  65. 2026-09-27 05:13 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  66. 2026-09-26 16:49 UTCEG score recompute
  67. 2026-09-26 16:49 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  68. 2026-09-26 15:59 UTCEPSS rescoreEPSS 0.7% · 52nd percentile
  69. 2026-09-26 04:09 UTCEG score recompute
  70. 2026-09-26 04:09 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  71. 2026-09-25 15:37 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  72. 2026-09-25 03:15 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1
  73. 2026-09-24 14:53 UTCEG score recompute
  74. 2026-09-24 14:53 UTCGHSA enrichmentGHSA-6h2j-ghfm-664v · GitHub severity CRITICAL · GitHub CVSS 8.1

Frequently asked(5)

What is CVE-2026-90562?
CVE-2026-90562 is a high-severity vulnerability; its CVE record was published on September 13, 2026. 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…
When was CVE-2026-90562 made public?
CVE-2026-90562 was made public on August 4, 2026: that is the date its CVE record's CNA, VulnCheck, gives for when the vulnerability was made public. The CVE record itself was published on September 13, 2026. EchelonGraph's copy of the record carries a last-modified date of September 24, 2026; the record at its source may have been updated since.
Is CVE-2026-90562 actively exploited?
CVE-2026-90562 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.7% probability of exploitation in the next 30 days (54th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-90562?
CVE-2026-90562 has a CVSS base score of 8.1 (the CNA's own assessment, by vulncheck; NVD's own analysis pending).
How do I remediate CVE-2026-90562?
A fix for CVE-2026-90562 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-90562 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-90562

Explore →

Is Your Infrastructure Affected by CVE-2026-90562?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.