CVE-2026-2614

HIGHPre-NVD 7.57.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 2.9%, top 14% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 3.2%CVSS: 7.5Exploit: Elevated riskExposed services: Not assessed

A fix is available — apply it.

A vulnerability in the _create_model_version() handler of mlflow/server/handlers.py in mlflow/mlflow versions 3.9.0 and earlier allows an unauthenticated remote attacker to read arbitrary files from the server's filesystem. The issue arises when a CreateModelVersion request includes the tag mlflow.prompt.is_prompt, which bypasses source path validation. This enables an attacker to store an arbitrary local filesystem path as the model version source. The get_model_version_artifact_handler() function later uses this source to serve files without verifying the model version's prompt status, leading to a complete confidentiality compromise. This issue is fixed in version 3.10.0.

CVSS v3
7.5
EG Score
7.5HIGHmedium confidence
EG Risk
65
EG Risk 65/100

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
Severity75% × 45%
Exploitation40% × 40%
Automatability100% × 15%
EPSS PROB
3.2%
EPSS %ILE
87th
KEV
Not listed

Published

May 11, 2026

Last Modified

August 28, 2026

Advisory Details (2)

Auto-updated May 11, 2026
Patch available.
generic

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

https://huntr.com/bounties/19380271-3fbf-4beb-987e-6fd7069c55e6
generic

Fix arbitrary file read via prompt tag validation bypass in Model Reg… · mlflow/mlflow@6e801f4 · GitHub

https://github.com/mlflow/mlflow/commit/6e801f4259d96804c73107315b24cef0f6aa115a

Vendor Advisories for CVE-2026-2614(4)

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

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-workbench-jupyter-trustyai-cpu-py312-rhel9:17870735932026-08-27redhat
redhatrhoai/odh-training-cuda128-torch29-py312-rhel9:17829911702026-07-09redhat
redhatrhoai/odh-training-cuda128-torch29-py312-rhel9:17821322402026-07-01redhat

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.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 8× in last 7d / 24× 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.

Showing the most recent 100 of 222 total refreshes for this CVE.

  1. 2026-10-09 20:07 UTCEPSS rescore
  2. 2026-10-08 17:12 UTCEPSS rescore
  3. 2026-10-07 23:47 UTCEPSS rescore
  4. 2026-10-06 15:17 UTCEPSS rescore
  5. 2026-10-06 09:19 UTCOSV refresh
  6. 2026-10-05 17:42 UTCEPSS rescore
  7. 2026-10-04 23:21 UTCEPSS rescore
  8. 2026-10-03 14:25 UTCEPSS rescore
  9. 2026-10-01 19:49 UTCEPSS rescore
  10. 2026-09-30 15:03 UTCEPSS rescore
  11. 2026-09-28 13:51 UTCEPSS rescore
  12. 2026-09-26 15:58 UTCEPSS rescore
  13. 2026-09-26 00:26 UTCEPSS rescore
  14. 2026-09-20 20:15 UTCEPSS rescore
  15. 2026-09-20 20:15 UTCEPSS rescore
  16. 2026-09-18 19:28 UTCEPSS rescore
  17. 2026-09-18 19:27 UTCEPSS rescore
  18. 2026-09-17 19:30 UTCEPSS rescore
  19. 2026-09-16 16:39 UTCOSV refresh
  20. 2026-09-16 14:08 UTCEPSS rescore
  21. 2026-09-16 05:15 UTCEPSS rescore
  22. 2026-09-12 15:01 UTCEPSS rescore
  23. 2026-09-11 14:52 UTCEPSS rescore
  24. 2026-09-10 09:34 UTCEPSS rescore
  25. 2026-09-08 22:00 UTCEPSS rescore
Show 75 more
  1. 2026-09-07 16:01 UTCEPSS rescore
  2. 2026-09-06 13:47 UTCEPSS rescore
  3. 2026-09-06 13:47 UTCEPSS rescore
  4. 2026-09-04 05:06 UTCEPSS rescore
  5. 2026-09-02 14:11 UTCEPSS rescore
  6. 2026-09-01 13:53 UTCEPSS rescore
  7. 2026-09-01 04:39 UTCEPSS rescore
  8. 2026-09-01 04:39 UTCEPSS rescore
  9. 2026-08-30 19:17 UTCEPSS rescore
  10. 2026-08-30 01:22 UTCEPSS rescore
  11. 2026-08-28 21:41 UTCEPSS rescore
  12. 2026-08-28 16:47 UTCEG score recompute
  13. 2026-08-28 16:47 UTCVendor advisory
  14. 2026-08-28 16:00 UTCEG score recompute
  15. 2026-08-28 16:00 UTCVendor advisory
  16. 2026-08-27 14:25 UTCEPSS rescore
  17. 2026-08-26 14:46 UTCEPSS rescore
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-24 14:17 UTCEPSS rescore
  20. 2026-08-23 18:37 UTCEG score recompute
  21. 2026-08-23 18:37 UTCVendor advisory
  22. 2026-08-23 00:19 UTCEPSS rescore
  23. 2026-08-21 23:49 UTCEPSS rescore
  24. 2026-08-20 22:55 UTCEPSS rescore
  25. 2026-08-20 22:55 UTCEPSS rescore
  26. 2026-08-19 17:03 UTCEPSS rescore
  27. 2026-08-18 13:48 UTCEPSS rescore
  28. 2026-08-17 13:47 UTCEPSS rescore
  29. 2026-08-17 11:03 UTCEG score recompute
  30. 2026-08-17 11:03 UTCVendor advisory
  31. 2026-08-16 14:56 UTCEPSS rescore
  32. 2026-08-16 04:24 UTCEG score recompute
  33. 2026-08-16 04:24 UTCVendor advisory
  34. 2026-08-16 02:14 UTCEPSS rescore
  35. 2026-08-15 01:30 UTCEPSS rescore
  36. 2026-08-14 15:59 UTCVendor advisory
  37. 2026-08-14 02:56 UTCEG score recompute
  38. 2026-08-14 02:56 UTCVendor advisory
  39. 2026-08-13 22:00 UTCEPSS rescore
  40. 2026-08-13 05:57 UTCVendor advisory
  41. 2026-08-12 16:29 UTCEG score recompute
  42. 2026-08-12 16:29 UTCVendor advisory
  43. 2026-08-12 13:50 UTCEPSS rescore
  44. 2026-08-11 15:46 UTCEG score recompute
  45. 2026-08-11 15:46 UTCVendor advisory
  46. 2026-08-11 01:10 UTCEG score recompute
  47. 2026-08-11 01:10 UTCVendor advisory
  48. 2026-08-11 00:00 UTCEPSS rescore
  49. 2026-08-10 04:20 UTCVendor advisory
  50. 2026-08-09 15:17 UTCEG score recompute
  51. 2026-08-09 15:17 UTCVendor advisory
  52. 2026-08-09 13:46 UTCEPSS rescore
  53. 2026-08-09 02:14 UTCEG score recompute
  54. 2026-08-09 02:14 UTCVendor advisory
  55. 2026-08-08 16:37 UTCEPSS rescore
  56. 2026-08-08 03:43 UTCEG score recompute
  57. 2026-08-08 03:43 UTCVendor advisory
  58. 2026-08-07 14:40 UTCVendor advisory
  59. 2026-08-07 01:36 UTCEG score recompute
  60. 2026-08-07 01:36 UTCVendor advisory
  61. 2026-08-06 13:46 UTCEPSS rescore
  62. 2026-08-06 11:00 UTCVendor advisory
  63. 2026-08-05 21:56 UTCEG score recompute
  64. 2026-08-05 21:56 UTCVendor advisory
  65. 2026-08-05 19:17 UTCEPSS rescore
  66. 2026-08-04 15:10 UTCEPSS rescore
  67. 2026-08-03 19:26 UTCEG score recompute
  68. 2026-08-03 19:26 UTCVendor advisory
  69. 2026-08-03 10:36 UTCEPSS rescore
  70. 2026-08-03 03:32 UTCVendor advisory
  71. 2026-08-02 14:17 UTCEG score recompute
  72. 2026-08-02 14:17 UTCVendor advisory
  73. 2026-08-02 02:26 UTCEPSS rescore
  74. 2026-08-02 01:14 UTCEG score recompute
  75. 2026-08-02 01:14 UTCVendor advisory

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-2614.yaml
    First seen Jan 1, 2026

    MLflow <= 3.9.0 - Arbitrary File Read

    Open source ↗

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-2614?
CVE-2026-2614 is a high vulnerability published on May 11, 2026. A vulnerability in the createmodelversion() handler of mlflow/server/handlers.py in mlflow/mlflow versions 3.9.0 and earlier allows an unauthenticated remote attacker to read arbitrary files from the server's filesystem. The issue arises when a CreateModelVersion request includes the tag…
When was CVE-2026-2614 disclosed?
CVE-2026-2614 was first published on May 11, 2026, with the most recent update on August 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-2614 actively exploited?
CVE-2026-2614 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.2% probability of exploitation in the next 30 days (87th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-2614?
CVE-2026-2614 has a CVSS base score of 7.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-2614?
A fix for CVE-2026-2614 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-2614 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-2614

Explore →

Is Your Infrastructure Affected by CVE-2026-2614?

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

Book a Demo →Browse All CVEs