CVE-2026-2614

HIGHCVSS 7.57.5
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.5 under NVD CVSS v3. EPSS exploit probability: 0.7%, top 50% 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, nvd
Elevated
7.5
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 7.5Exploit: NoneExposed: 0

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

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.5(medium)
EPSS
48.5%
KEV
Not listed

Published

May 11, 2026

Last Modified

July 6, 2026

Advisory Details (2)

Auto-updated May 11, 2026
No patch confirmed yet.
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(2)

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

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
mlflow0.0.1 ... 3.9.0rc0 (171 versions)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 / 66× 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 117 total refreshes for this CVE.

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

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 in the National Vulnerability Database on May 11, 2026, with the most recent update on July 6, 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 48.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-2614?
CVE-2026-2614 has a CVSS v3 base score of 7.5 (NVD).
How do I remediate CVE-2026-2614?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-2614, 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

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.