CVE-2026-2652

HIGHNVD 8.68.6
EchelonGraph scoreMEDIUM confidence

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

Score 8.6 from GitHub Security Advisory (severity: HIGH) published 2026-05-15. NVD baseline CVSS 8.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: EPSS, GitHub Security Advisory, NVD CVSS v3
Elevated

Also known asEUVD-2026-30499 (ENISA EUVD) · GHSA-75cm-x2w3-8mgf (GitHub Security Advisories) · PYSEC-2026-2221 (OSV.dev)Source: ENISA EUVD

8.6EG
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: 21%CVSS: 8.6Exploit: No code on recordExposed services: Not assessed

A fix is available — apply it.

A vulnerability in mlflow/mlflow versions 3.9.0 and earlier allows unauthenticated access to certain FastAPI routes when the server is started with authentication enabled (--app-name basic-auth) and served via uvicorn (ASGI). The FastAPI permission middleware only enforces authentication on /gateway/ routes, leaving other routes such as the Job API (/ajax-api/3.0/jobs/*) and the OpenTelemetry trace ingestion API (/v1/traces) unprotected. This allows unauthenticated remote attackers to submit jobs, read job results, cancel running jobs, and inject arbitrary trace data into experiments. The issue arises from an architectural mismatch between Flask and FastAPI authentication mechanisms, where the _find_fastapi_validator() function fails to handle non-/gateway/ paths, resulting in a complete authentication bypass. This vulnerability is fixed in version 3.10.0.

CVSS v3
8.6
EG Score
8.6HIGHmedium confidence
EG Risk
70
EG Risk 70/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)
Severity86% × 45%
Impact severity (EG Severity): CVSS 8.6 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.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation public PoC (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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
21%
EPSS %ILE
97th
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.6): severity, escalated by confirmed exploitation. This CVE's 8.6 is its impact severity (EG Severity), not escalated.

EG Severity
8.6 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
21% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-11). 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 or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days 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 or medium mission impact; Attend at high (mission-essential systems).

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 yes (CISA Vulnrichment) · Technical impact partial (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; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (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

May 15, 2026

Last Modified

November 11, 2026

Advisory Details (2)

Auto-updated May 15, 2026
Patch available.
Web page

huntr - The world’s first bug bounty platform for AI/ML

https://huntr.com/bounties/5aeff5f0-49c7-4180-b5cb-c9a046f16756
Web page

Add missing authentication for fastapi routes (#20920) · mlflow/mlflow@bb62e77 · GitHub

https://github.com/mlflow/mlflow/commit/bb62e773263c14e9ba4d1a82fe72d0de2442c6aa

Vendor Advisories for CVE-2026-2652(1)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
pipmlflow @ 3.11.0 (fixes < 3.11.0)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
mlflow0.0.1 ... 3.9.0rc0 (171 versions)
  • every version up to 3.11.0: fixed in 3.11.0
  • every version up to 3.10.0: fixed in 3.10.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 32× 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 its CVE.org record (CNA or CISA ADP). 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). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 234 rows on record for this CVE, as 97 entries (3 repeats merged).

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. 3 repeat rows among the latest 100 are merged into the row they repeat. The 134 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-12 16:33 UTCEPSS rescoreEPSS 21% · 97th percentile
  2. 2026-11-11 20:37 UTCEchelonGraph re-scored
  3. 2026-11-11 20:37 UTCGHSA enrichmentGHSA-75cm-x2w3-8mgf · GitHub severity HIGH · GitHub CVSS 8.6
  4. 2026-11-11 16:39 UTCEPSS rescoreEPSS 21% · 97th percentile
  5. 2026-11-10 16:43 UTCEPSS rescoreEPSS 21% · 97th percentile
  6. 2026-11-09 16:35 UTCEPSS rescoreEPSS 21% · 97th percentile
  7. 2026-11-08 16:39 UTCEPSS rescoreEPSS 21% · 97th percentile
  8. 2026-11-07 16:38 UTCEPSS rescoreEPSS 21% · 97th percentile
  9. 2026-11-07 06:01 UTCEchelonGraph re-scored
  10. 2026-11-07 06:01 UTCGHSA enrichmentGHSA-75cm-x2w3-8mgf · GitHub severity HIGH · GitHub CVSS 8.6
  11. 2026-11-06 16:37 UTCEPSS rescoreEPSS 21% · 97th percentile
  12. 2026-11-05 16:37 UTCEPSS rescoreEPSS 21% · 97th percentile
  13. 2026-11-04 16:35 UTCEPSS rescoreEPSS 21% · 97th percentile
  14. 2026-11-03 16:47 UTCEPSS rescoreEPSS 21% · 97th percentile
  15. 2026-11-02 16:44 UTCEPSS rescoreEPSS 21% · 97th percentile
  16. 2026-11-01 16:34 UTCEPSS rescoreEPSS 21% · 97th percentile
  17. 2026-10-31 16:32 UTCEPSS rescoreEPSS 21% · 97th percentile
  18. 2026-10-31 09:33 UTCEchelonGraph re-scored
  19. 2026-10-30 16:34 UTCEPSS rescoreEPSS 21% · 97th percentile
  20. 2026-10-29 16:33 UTCEPSS rescoreEPSS 21% · 97th percentile
  21. 2026-10-28 16:32 UTCEPSS rescoreEPSS 21% · 97th percentile
  22. 2026-10-27 16:31 UTCEPSS rescoreEPSS 21% · 97th percentile
  23. 2026-10-26 16:31 UTCEPSS rescoreEPSS 21% · 97th percentile
  24. 2026-10-25 16:32 UTCEPSS rescoreEPSS 21% · 97th percentile
  25. 2026-10-25 14:39 UTCEchelonGraph re-scored
Show 72 more
  1. 2026-10-24 16:32 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  2. 2026-10-24 13:07 UTCEchelonGraph re-scored
  3. 2026-10-23 16:31 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  4. 2026-10-22 16:34 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  5. 2026-10-21 16:32 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  6. 2026-10-20 16:32 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  7. 2026-10-19 16:31 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  8. 2026-10-18 16:31 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  9. 2026-10-18 03:51 UTCEchelonGraph re-scored
  10. 2026-10-17 16:36 UTCEchelonGraph re-scored
  11. 2026-10-17 16:33 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  12. 2026-10-16 16:41 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  13. 2026-10-15 16:31 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  14. 2026-10-14 16:32 UTCEPSS rescoreEPSS 1.4% · 72nd percentile
  15. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  16. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  17. 2026-10-12 16:18 UTCEchelonGraph re-scored
  18. 2026-10-11 20:00 UTCEchelonGraph re-scored
  19. 2026-10-11 17:13 UTCEchelonGraph re-scored
  20. 2026-10-11 14:45 UTCEchelonGraph re-scored
  21. 2026-10-11 13:48 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  22. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  23. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  24. 2026-10-08 17:12 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  25. 2026-10-07 23:47 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  26. 2026-10-06 15:17 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  27. 2026-10-05 17:42 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  28. 2026-10-03 14:25 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  29. 2026-10-01 19:49 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  30. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  31. 2026-09-30 04:28 UTCOSV refresh
  32. 2026-09-26 15:58 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  33. 2026-09-26 00:26 UTCEPSS rescoreEPSS 1.4% · 71st percentile
  34. 2026-09-18 19:27 UTCEPSS rescoreEPSS 21% · 97th percentile
  35. 2026-09-17 19:30 UTCEPSS rescoreEPSS 21% · 97th percentile
  36. 2026-09-16 14:08 UTCEPSS rescoreEPSS 21% · 97th percentile
  37. 2026-09-16 05:15 UTCEPSS rescoreEPSS 21% · 97th percentile
  38. 2026-09-12 15:01 UTCEPSS rescoreEPSS 21% · 97th percentile
  39. 2026-09-11 14:52 UTCEPSS rescoreEPSS 21% · 97th percentile
  40. 2026-09-11 07:23 UTCOSV refresh
  41. 2026-09-10 09:34 UTCEPSS rescoreEPSS 21% · 97th percentile
  42. 2026-09-08 22:00 UTCEPSS rescoreEPSS 21% · 97th percentile
  43. 2026-09-06 13:47 UTCEPSS rescoreEPSS 21% · 97th percentile
  44. 2026-09-04 05:06 UTCEPSS rescoreEPSS 21% · 97th percentile
  45. 2026-09-02 14:11 UTCEPSS rescoreEPSS 21% · 97th percentile
  46. 2026-09-01 13:53 UTCEPSS rescoreEPSS 21% · 97th percentile
  47. 2026-08-30 19:17 UTCEPSS rescoreEPSS 21% · 97th percentile
  48. 2026-08-30 01:22 UTCEPSS rescoreEPSS 21% · 97th percentile
  49. 2026-08-28 21:41 UTCEPSS rescoreEPSS 21% · 97th percentile
  50. 2026-08-27 14:25 UTCEPSS rescoreEPSS 21% · 97th percentile
  51. 2026-08-26 14:46 UTCEPSS rescoreEPSS 21% · 97th percentile
  52. 2026-08-25 13:49 UTCEPSS rescoreEPSS 21% · 97th percentile
  53. 2026-08-24 14:17 UTCEPSS rescoreEPSS 21% · 97th percentile
  54. 2026-08-22 01:35 UTCEchelonGraph re-scored
  55. 2026-08-21 23:49 UTCEPSS rescoreEPSS 19% · 97th percentile
  56. 2026-08-20 22:55 UTCEPSS rescoreEPSS 19% · 97th percentile
  57. 2026-08-20 19:28 UTCEchelonGraph re-scored
  58. 2026-08-19 17:03 UTCEPSS rescoreEPSS 19% · 97th percentile
  59. 2026-08-18 13:48 UTCEPSS rescoreEPSS 19% · 97th percentile
  60. 2026-08-17 10:18 UTCEchelonGraph re-scored
  61. 2026-08-16 14:56 UTCEPSS rescoreEPSS 19% · 97th percentile
  62. 2026-08-16 03:51 UTCEchelonGraph re-scored
  63. 2026-08-16 02:14 UTCEPSS rescoreEPSS 19% · 97th percentile
  64. 2026-08-15 01:30 UTCEPSS rescoreEPSS 19% · 97th percentile
  65. 2026-08-14 02:20 UTCEchelonGraph re-scored
  66. 2026-08-13 22:00 UTCEPSS rescoreEPSS 19% · 97th percentile
  67. 2026-08-12 14:53 UTCEchelonGraph re-scored
  68. 2026-08-12 13:50 UTCEPSS rescoreEPSS 19% · 97th percentile
  69. 2026-08-11 14:01 UTCEchelonGraph re-scored
  70. 2026-08-10 00:49 UTCEchelonGraph re-scored
  71. 2026-08-09 13:46 UTCEPSS rescoreEPSS 19% · 97th percentile
  72. 2026-08-09 01:47 UTCEchelonGraph re-scored

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2026/CVE-2026-2652.yaml
    Published Jun 4, 2026

    MLflow < 3.10.0 - Authentication Bypass on FastAPI Routes

    Open source ↗

Frequently asked(5)

What is CVE-2026-2652?
CVE-2026-2652 is a high-severity vulnerability; its CVE record was published on May 15, 2026. A vulnerability in mlflow/mlflow versions 3.9.0 and earlier allows unauthenticated access to certain FastAPI routes when the server is started with authentication enabled (--app-name basic-auth) and served via uvicorn (ASGI). The FastAPI permission middleware only enforces authentication on…
When was the CVE record for CVE-2026-2652 published?
The CVE record for CVE-2026-2652 was published on May 15, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 11, 2026; the record at its source may have been updated since.
Is CVE-2026-2652 actively exploited?
CVE-2026-2652 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 21% probability of exploitation in the next 30 days (97th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-2652?
CVE-2026-2652 has a CVSS v3 base score of 8.6 (NVD).
How do I remediate CVE-2026-2652?
A fix for CVE-2026-2652 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-2652 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-2652

Explore →

Is Your Infrastructure Affected by CVE-2026-2652?

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