Security Digest · Vulnerability record
CVE-2024-27132: Cross-site Scripting in MLFlow
Insufficient sanitization in MLflow leads to XSS when running an untrusted recipe.
CVSS 7.5 High EPSS 0.9% · p59
Should you act?
Normal patch cycle
No exploitation signal; fix it in your next routine update if you are affected. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- Not in CISA KEV, but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 0.9%, percentile 59: FIRST’s model estimates a 0.9% chance of exploitation activity in the next 30 days, higher than 59% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Needs a user to click or open something. Phishing makes that realistic, but it is not wormable.
- Only applies if your dependency tree includes
mlflow(PyPI) < 2.10.0, fixed in 2.10.0. Check your lockfile, including transitive dependencies.
What it is
Insufficient sanitization in MLflow leads to XSS when running an untrusted recipe. This issue leads to a client-side RCE when running an untrusted recipe in Jupyter Notebook. The vulnerability stems from lack of sanitization over template variables.
From the GitHub advisory
Insufficient sanitization in MLflow leads to XSS when running an untrusted recipe.
This issue leads to a client-side RCE when running an untrusted recipe in Jupyter Notebook.
The vulnerability stems from lack of sanitization over template variables.
Weakness type: CWE-79.
Product: mlflow (PyPI) · Assigned by: JFROG · Published: 2024-02-23
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| PyPI | mlflow | < 2.10.0 | 2.10.0 |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| mlflow | <= 2.9.2 |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| JFROG | 3.1 | 7.5 High | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.6 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H |
- Attack vector: network (remotely reachable)
- Attack complexity: high (needs special conditions)
- Privileges required: none (no login)
- User interaction: required (a user must click/open something)
- Scope: unchanged
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc, automatable no, technical impact total.
- FIRST EPSS (model of 2026-10-21): 0.88% probability of exploitation activity in the next 30 days; percentile 59.
Timeline
- — CVE record published by JFROG
- — GitHub-reviewed advisory GHSA-6749-m5cp-6cg7 published (critical)
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-6749-m5cp-6cg7 github.com
- CVE.org record CVE-2024-27132 cve.org
- NVD entry CVE-2024-27132 nvd.nist.gov
Other references from the CVE record and advisory
- research.jfrog.com research.jfrog.com
- github.com github.com
- github.com github.com