CVE-2026-4137

HIGHNVD 7.87.8
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.2% (9th percentile of EPSS-scored CVEs). GitHub Security Advisory CVSS 7.0 is lower than this score; a lower GitHub score revises it only when its advisory is newer than the CVE record's last change, and this advisory (published 2026-05-18) is not newer than that change (2026-07-24), so it does not.

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

Also known asEUVD-2026-30807 (ENISA EUVD) · GHSA-f2m9-wcf4-cwwx (GitHub Security Advisories)Source: ENISA EUVD

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

A fix is available — apply it.

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.8HIGHmedium confidence
EG Risk
51
EG Risk 51/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)
Severity78% × 45%
Impact severity (EG Severity): CVSS 7.8 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.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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
0.2%
EPSS %ILE
9th
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 (7.8): severity, escalated by confirmed exploitation. This CVE's 7.8 is its impact severity (EG Severity), not escalated.

EG Severity
7.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.2% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-30). 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, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade 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, Track* at medium and Attend at high mission impact.

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 no (CISA Vulnrichment) · Technical impact total (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; Fix on system upgrade if it is not.

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

Last Modified

July 24, 2026

Advisory Details (2)

Auto-updated Jun 4, 2026
Patch available. Sources: github_commit.
Web page

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 rangeFix by version rangeDependents
mlflow0.0.1 ... 3.9.0rc0 (175 versions)
  • 1.26.0 up to 3.11.0: fixed in 3.11.0
  • every version up to 3.11.0: fixed in 3.11.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 38× 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 it from the CNA feed. 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). Most recent first.

Showing the most recent 100 of 193 refreshes on record for this CVE.

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. None are among the latest 100 rows. The 93 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-4137?
CVE-2026-4137 is a high-severity vulnerability; its CVE record was published on May 18, 2026. 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…
When was the CVE record for CVE-2026-4137 published?
The CVE record for CVE-2026-4137 was published on May 18, 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 July 24, 2026; the record at its source may have been updated since.
Is CVE-2026-4137 actively exploited?
CVE-2026-4137 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (9th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-4137?
CVE-2026-4137 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-4137?
A fix for CVE-2026-4137 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-4137 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-4137

Explore →

Is Your Infrastructure Affected by CVE-2026-4137?

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

Book a Demo →Browse All CVEs