Is mlflow affected by CVE-2026-4137?

PyPI mlflow is affected in <3.11.0.

Is CVE-2026-4137 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.2%.

high

CVE-2026-4137

Q: Is CVE-2026-4137 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.2%.

PyPI · mlflow

Summary

MLFlow Creates a Temporary File With Insecure Permissions

Severity: high
EPSS: 0.2% (p9)
Also known as: GHSA-f2m9-wcf4-cwwx, BIT-mlflow-2026-4137
Published: 2026-05-18

References

https://nvd.nist.gov/vuln/detail/CVE-2026-4137
https://github.com/mlflow/mlflow/commit/1dcbb0c2fbd1f446c328830e601ca13a28219b8a
https://github.com/advisories/GHSA-4x5p-f36r-mxxr

Related advisories

CVE-2026-2611 — critical · PyPI/mlflow
CVE-2026-0545 — critical · PyPI/mlflow
CVE-2026-0596 — critical · PyPI/mlflow
CVE-2025-15379 — critical · PyPI/mlflow
CVE-2025-15036 — critical · PyPI/mlflow
CVE-2026-2635 — critical · PyPI/mlflow
CVE-2026-2652 — high · PyPI/mlflow
CVE-2026-2614 — high · PyPI/mlflow

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.