CVE-2026-33865
mediumpriority · track · 22EPSS 0.002 · 12 %ileEUUSEPSS · scored 2026-10-27
MLflow is vulnerable to Stored Cross-Site Scripting (XSS) caused by unsafe parsing of YAML-based MLmodel artifacts in its web interface. An authenticated attacker can upload a malicious MLmodel file containing a payload that executes when another user views the artifact in the UI. This allows actions such as session hijacking or performing operations on behalf of the victim. This issue affects MLflow version through 3.10.1
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode⚠ sources disagree · low–medium · 1.2–5.4
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (5)
Products and version ranges known to be affected.
advisories (3)
Vendor and ecosystem advisories describing this.
- GHSA-fh64-r2vc-xvhrMLflow is vulnerable to Stored Cross-Site Scripting (XSS) caused by unsafe parsing of YAML-based MLmodel artifacts in its web interface2026-04-07ghsa · osvUS
MLflow is vulnerable to Stored Cross-Site Scripting (XSS) caused by unsafe parsing of YAML-based MLmodel artifacts in its web interface. An authenticated attacker can upload a malicious MLmodel file containing a payload that executes when another user views the artifact in the UI. This allows actions such as session hijacking or performing operations on behalf of the victim. This issue affects MLflow version through 3.10.1
- BIT-mlflow-2026-33865Stored XSS via unsafe YAML parsing in MLflow2026-04-21vendor · osvUS
MLflow is vulnerable to Stored Cross-Site Scripting (XSS) caused by unsafe parsing of YAML-based MLmodel artifacts in its web interface. An authenticated attacker can upload a malicious MLmodel file containing a payload that executes when another user views the artifact in the UI. This allows actions such as session hijacking or performing operations on behalf of the victim. This issue affects MLflow version through 3.10.1
- PYSEC-2026-932026-04-07vendor · osvUS
MLflow is vulnerable to Stored Cross-Site Scripting (XSS) caused by unsafe parsing of YAML-based MLmodel artifacts in its web interface. An authenticated attacker can upload a malicious MLmodel file containing a payload that executes when another user views the artifact in the UI. This allows actions such as session hijacking or performing operations on behalf of the victim. This issue affects MLflow version through 3.10.1
also known as (7)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (8)
External citations — patches, advisories, analysis.
- https://cert.pl/en/posts/2026/04/CVE-2026-33865/cnnvd
- https://github.com/mlflow/mlflow/pull/21435cnnvd
- https://afine.com/blogs/attacking-mlflow-how-ml-artifacts-become-attack-vectorsenisa_euvd
- https://cert.pl/en/posts/2026/04/CVE-2026-33865/enisa_euvd
- https://github.com/mlflow/mlflow/pull/21435enisa_euvd
- https://afine.com/blogs/attacking-mlflow-how-ml-artifacts-become-attack-vectorsExploitThird Party Advisorynvd
- https://cert.pl/en/posts/2026/04/CVE-2026-33865/Third Party Advisorynvd
- https://github.com/mlflow/mlflow/pull/21435Issue TrackingPatchnvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan