What is the severity of CVE-2024-37058?

CVE-2024-37058 is considered a high severity vulnerability due to its potential to allow arbitrary code execution.

How do I fix CVE-2024-37058?

To mitigate CVE-2024-37058, it is recommended to upgrade MLflow to a version newer than 2.14.1.

What versions of MLflow are affected by CVE-2024-37058?

CVE-2024-37058 affects MLflow versions 2.5.0 through 2.14.1.

What kind of attack does CVE-2024-37058 enable?

CVE-2024-37058 enables an attacker to execute arbitrary code on an end user’s system through maliciously uploaded models.

What is the cause of CVE-2024-37058?

CVE-2024-37058 is caused by the deserialization of untrusted data within the MLflow platform.

Vulnerability/
CVE-2024-37058

high

8.8

CWE

502

4/6/2024

3/2/2025

CVE-2024-37058

First published: Tue Jun 04 2024(Updated: )

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.

Credit: 6f8de1f0-f67e-45a6-b68f-98777fdb759c 6f8de1f0-f67e-45a6-b68f-98777fdb759c

Affected Software	Affected Version	How to fix
pip/mlflow	>=2.5.0<=2.14.1
MLflow	>=2.5.0

Never miss a vulnerability like this again

Reference Links

Frequently Asked Questions

What is the severity of CVE-2024-37058?
CVE-2024-37058 is considered a high severity vulnerability due to its potential to allow arbitrary code execution.
How do I fix CVE-2024-37058?
To mitigate CVE-2024-37058, it is recommended to upgrade MLflow to a version newer than 2.14.1.
What versions of MLflow are affected by CVE-2024-37058?
CVE-2024-37058 affects MLflow versions 2.5.0 through 2.14.1.
What kind of attack does CVE-2024-37058 enable?
CVE-2024-37058 enables an attacker to execute arbitrary code on an end user’s system through maliciously uploaded models.
What is the cause of CVE-2024-37058?
CVE-2024-37058 is caused by the deserialization of untrusted data within the MLflow platform.

agent/type
agent/first-publish-date
agent/weakness
agent/description
agent/severity
agent/references
collector/nvd-cve
source/NVD
agent/author
collector/github-advisory-latest
source/GitHub
alias/GHSA-cwgg-w6mp-w9hg
alias/CVE-2024-37058
agent/software-canonical-lookup
collector/github-advisory
collector/mitre-cve
source/MITRE
agent/trending
agent/source
collector/nvd-api
agent/last-modified-date
agent/softwarecombine
agent/tags
agent/event
package-manager/pip
vendor/lfprojects
canonical/mlflow
version/mlflow/2.5.0

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co

By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.

Frequently Asked Questions

What is the severity of CVE-2024-37058?
CVE-2024-37058 is considered a high severity vulnerability due to its potential to allow arbitrary code execution.
How do I fix CVE-2024-37058?
To mitigate CVE-2024-37058, it is recommended to upgrade MLflow to a version newer than 2.14.1.
What versions of MLflow are affected by CVE-2024-37058?
CVE-2024-37058 affects MLflow versions 2.5.0 through 2.14.1.
What kind of attack does CVE-2024-37058 enable?
CVE-2024-37058 enables an attacker to execute arbitrary code on an end user’s system through maliciously uploaded models.
What is the cause of CVE-2024-37058?
CVE-2024-37058 is caused by the deserialization of untrusted data within the MLflow platform.