CVE-2024-37058
Telemetry drift only. No threshold crossed and no authority ruling changed.
CVE record, CISA KEV and EPSS as of 2026-10-18.
CVEs like this one computed, by meaning
What to do now held facts and links
- No fix version is held. The CNA's first reference is the place to look: hiddenlayer.com
- Record your decision, dated and frozen with today's evidence: patch by a date · mitigated by a compensating control · deferred · accepted the risk · not affected
- Check your version against the ranges this record publishes.
What it is stated by the CNA
Deserialization of untrusted data can occur in versions of the MLflow platform running version 2.5.0 or newer, enabling a maliciously uploaded Langchain AgentExecutor model to run arbitrary code on an end user’s system when interacted with.
- weakness
- CWE-502 Deserialization of Untrusted Data
- affected
- MLflow
- published ranges
- lfprojects mlflow >= 2.5.0
- fixed in
- No fix version in held sources.
- fixed by package (from OSV advisories)
- mlflow (Bitnami): 2.14.2 BIT-mlflow-2024-37058
- later fixes (from OSV advisories)
- mlflow 2.14.2 is inside a range CVE-2024-27134 (BIT-mlflow-2024-27134) lists as affected. That advisory is fixed in 2.16.0.mlflow 2.14.2 is inside a range CVE-2025-10279 (BIT-mlflow-2025-10279) lists as affected. That advisory is fixed in 3.4.0.mlflow 2.14.2 is inside a range CVE-2025-11200 (BIT-mlflow-2025-11200) lists as affected. That advisory is fixed in 2.21.1.mlflow 2.14.2 is inside a range CVE-2025-11201 (BIT-mlflow-2025-11201) lists as affected. That advisory is fixed in 3.0.0.mlflow 2.14.2 is inside a range CVE-2025-14279 (BIT-mlflow-2025-14279) lists as affected. That advisory is fixed in 3.5.0.mlflow 2.14.2 is inside a range CVE-2025-14287 (BIT-mlflow-2025-14287) lists as affected. That advisory is fixed in 3.7.0.
- severity
- 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
- assigned by
- HiddenLayer
- published
- 2024-06-04
check us hiddenlayer.com
Exploit code held, dated
- exploit code
- None held in the PoC-in-GitHub feed. A public repository changes this brief.
What moved held, dated
| date | EPSS | event |
|---|---|---|
| 6 Jun 2024 | 0.00043 | |
| 4 Feb 2025 | 0.00093 | |
| 17 Mar 2025 | 0.00226 | scoring model v2025.03.14 |
| 21 Mar 2025 | 0.00247 | |
| 21 Nov 2025 | 0.00522 | |
| 14 Mar 2026 | 0.00399 | |
| 15 Jun 2026 | 0.00618 | scoring model v2026.06.15 |
| 15 Oct 2026 | 0.00623 |
17 observations held. A step marked with a scoring model moved because the measurement was replaced, not because the vulnerability changed.
Outside the record researched, cited
This section reads the record's references and adds cited findings from outside it. It needs an account. Everything above is held facts and is complete without it.
What would change this brief held, dated
- CISA KEV
- Not listed in the catalogue we hold. A listing changes this brief.
- exploit probability
- 0.01 on 2026-10-15 (FIRST's EPSS, a probability and not evidence of exploitation). Next band line: 10% (0.10). Crossing a line changes this brief.
- fix
- No fix version is held. One published by the CNA or OSV changes this brief.
How to check this
Every value above is held with two dates: when it was true upstream (as_of) and when we recorded it (tx_from). Re-derive the exploit probability as it stood on any date:
SELECT value, source, source_version, as_of, tx_from
FROM volatile_valid_as_of('CVE-2024-37058', '2026-11-01T23:59:59.999999Z', now());