CVE-2026-85237

HIGHNVD 8.18.1
EchelonGraph scoreHIGH confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-09-03. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.1Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

A vulnerability in MISP's email-based one-time password (OTP) authentication flow allowed an attacker to perform an unrestricted number of OTP verification attempts.

The email_otp() endpoint did not apply brute-force protection when validating submitted OTP values. An attacker who had reached the OTP verification stage, for example after successfully providing a user's primary authentication credentials, could repeatedly submit candidate OTP values while the same OTP remained valid. This significantly increased the feasibility of guessing the OTP and bypassing the additional authentication factor, potentially resulting in unauthorized access to the affected user's account.

The issue was exacerbated by the fact that the OTP is associated with the user rather than with an individual pending login session, allowing multiple concurrent sessions to attempt guesses against the same valid OTP.

The patch integrates the existing MISP brute-force protection mechanism into the email OTP flow. Failed OTP attempts are now counted against the user, further attempts are rejected once the configured threshold is reached, and the active OTP is invalidated when the attempt budget is exhausted. Blocklisted users are also prevented from requesting the generation of a fresh OTP. In addition, OTP comparison now uses hash_equals() and validates that the submitted value is a string.

CVSS v3
8.1
EG Score
8.1(high)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

September 3, 2026

Last Modified

September 11, 2026

Advisory Details (1)

Auto-updated Sep 3, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
github_commit

commit 8658062ea (MISP/MISP)

Fix landed in MISP/MISP commit 8658062ea — awaiting tagged release

https://github.com/MISP/MISP/commit/8658062ea

Vendor Advisories for CVE-2026-85237(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 26× in last 7d / 60× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-09-19 19:30 UTCEG score recompute
  2. 2026-09-19 19:30 UTCGHSA enrichment
  3. 2026-09-19 06:22 UTCEG score recompute
  4. 2026-09-19 06:22 UTCGHSA enrichment
  5. 2026-09-18 19:28 UTCEPSS rescore
  6. 2026-09-18 17:13 UTCGHSA enrichment
  7. 2026-09-18 04:05 UTCEG score recompute
  8. 2026-09-18 04:05 UTCGHSA enrichment
  9. 2026-09-17 19:32 UTCEPSS rescore
  10. 2026-09-17 14:56 UTCGHSA enrichment
  11. 2026-09-17 01:48 UTCEG score recompute
  12. 2026-09-17 01:48 UTCGHSA enrichment
  13. 2026-09-16 14:09 UTCEPSS rescore
  14. 2026-09-16 12:40 UTCEG score recompute
  15. 2026-09-16 12:40 UTCGHSA enrichment
  16. 2026-09-16 05:15 UTCEPSS rescore
  17. 2026-09-15 23:32 UTCGHSA enrichment
  18. 2026-09-15 10:24 UTCEG score recompute
  19. 2026-09-15 10:23 UTCGHSA enrichment
  20. 2026-09-15 03:12 UTCEPSS rescore
  21. 2026-09-15 03:12 UTCEPSS rescore
  22. 2026-09-14 21:14 UTCGHSA enrichment
  23. 2026-09-14 08:06 UTCGHSA enrichment
  24. 2026-09-13 18:58 UTCEG score recompute
  25. 2026-09-13 18:58 UTCGHSA enrichment
Show 35 more
  1. 2026-09-13 05:50 UTCGHSA enrichment
  2. 2026-09-12 16:42 UTCEG score recompute
  3. 2026-09-12 16:42 UTCGHSA enrichment
  4. 2026-09-12 03:34 UTCEG score recompute
  5. 2026-09-12 03:34 UTCGHSA enrichment
  6. 2026-09-11 14:53 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 14:25 UTCEG score recompute 0.50
  9. 2026-09-11 14:25 UTCGHSA enrichment
  10. 2026-09-11 14:22 UTCNVD updateCVSS v3 → 8.1
  11. 2026-09-11 03:40 UTCGHSA enrichment
  12. 2026-09-10 14:32 UTCEG score recompute
  13. 2026-09-10 14:32 UTCGHSA enrichment
  14. 2026-09-10 01:24 UTCGHSA enrichment
  15. 2026-09-09 12:16 UTCGHSA enrichment
  16. 2026-09-08 23:08 UTCEG score recompute
  17. 2026-09-08 23:08 UTCGHSA enrichment
  18. 2026-09-08 22:01 UTCEPSS rescore
  19. 2026-09-08 03:58 UTCGHSA enrichment
  20. 2026-09-07 14:50 UTCGHSA enrichment
  21. 2026-09-06 23:44 UTCEG score recompute
  22. 2026-09-06 23:44 UTCGHSA enrichment
  23. 2026-09-06 13:48 UTCEPSS rescore
  24. 2026-09-06 10:36 UTCGHSA enrichment
  25. 2026-09-05 21:28 UTCEG score recompute
  26. 2026-09-05 21:28 UTCGHSA enrichment
  27. 2026-09-05 15:31 UTCEPSS rescore
  28. 2026-09-05 08:21 UTCGHSA enrichment
  29. 2026-09-04 19:13 UTCEG score recompute
  30. 2026-09-04 19:13 UTCGHSA enrichment
  31. 2026-09-04 06:05 UTCGHSA enrichment
  32. 2026-09-03 16:33 UTCEG score recompute
  33. 2026-09-03 15:49 UTCEG score recompute
  34. 2026-09-03 15:35 UTCEG score recompute
  35. 2026-09-03 15:34 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-85237?
CVE-2026-85237 is a high vulnerability published on September 3, 2026. A vulnerability in MISP's email-based one-time password (OTP) authentication flow allowed an attacker to perform an unrestricted number of OTP verification attempts. The email_otp() endpoint did not apply brute-force protection when validating submitted OTP values. An attacker who had reached the…
When was CVE-2026-85237 disclosed?
CVE-2026-85237 was first published in the National Vulnerability Database on September 3, 2026, with the most recent update on September 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-85237 actively exploited?
CVE-2026-85237 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.0% of all scored CVEs.
What is the CVSS score of CVE-2026-85237?
CVE-2026-85237 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-85237?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-85237, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-85237?

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