CVE-2026-4137

HIGHNVD 7.87.0▼
EchelonGraph scoreMEDIUM confidence

Score 7.0 from GitHub Security Advisory (severity: HIGH) published 2026-05-18. NVD baseline CVSS 7.8; sources differ by 0.8.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
7.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.8Exploit: NoneExposed: 0

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

In mlflow/mlflow versions prior to 3.11.0, the get_or_create_nfs_tmp_dir() function in mlflow/utils/file_utils.py creates temporary directories with world-writable permissions (0o777), and the _create_model_downloading_tmp_dir() function in mlflow/pyfunc/__init__.py creates directories with group-writable permissions (0o770). These insecure permissions allow local attackers to tamper with model artifacts, such as cloudpickle-serialized Python objects, and achieve arbitrary code execution when the tampered artifacts are deserialized via cloudpickle.load(). This vulnerability is particularly critical in environments with shared NFS mounts, such as Databricks, where NFS is enabled by default. The issue is a continuation of the vulnerability class addressed in CVE-2025-10279, which was only partially fixed.

CVSS v3
7.8
EG Score
7.0(medium)
EPSS
9.2%
KEV
Not listed

Published

May 18, 2026

Last Modified

June 2, 2026

Advisory Details (2)

Auto-updated Jun 4, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit.
generic

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

https://huntr.com/bounties/648dc30b-76c7-4433-86b8-f43d926fd8d6
github_commit

commit 1dcbb0c2fbd1 (mlflow/mlflow)

Fix landed in mlflow/mlflow commit 1dcbb0c2fbd1 — awaiting tagged release

https://github.com/mlflow/mlflow/commit/1dcbb0c2fbd1f446c328830e601ca13a28219b8a

Vendor Advisories for CVE-2026-4137(1)

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 (175 versions)3.11.0—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 54× 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 106 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-4137?
CVE-2026-4137 is a high vulnerability published on May 18, 2026. In mlflow/mlflow versions prior to 3.11.0, the getorcreatenfstmpdir() function in mlflow/utils/fileutils.py creates temporary directories with world-writable permissions (0o777), and the createmodeldownloadingtmp_dir() function in mlflow/pyfunc/init.py creates directories with group-writable…
When was CVE-2026-4137 disclosed?
CVE-2026-4137 was first published in the National Vulnerability Database on May 18, 2026, with the most recent update on June 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-4137 actively exploited?
CVE-2026-4137 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 9.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-4137?
CVE-2026-4137 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 7.0.
How do I remediate CVE-2026-4137?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-4137, 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-4137

Explore →

Is Your Infrastructure Affected by CVE-2026-4137?

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

Start Free Scan →Browse All CVEs