CVE-2026-33865

Stored XSS via unsafe YAML parsing in MLflow

CVSS 5.1 MEDIUMEPSS 0.2%CWE-79

Vexday Risk Score

33Attention

SSVC decision (CISA)

Attend

PoC available → attend closely

CVSS 5.1EPSS 0.2%KEV nãoPoC públicaNuclei —Metasploit —Patch referenciado

Lifecycle

07 Apr 2026Published on NVD

Recommendation: Plan a near-term fix — a public PoC already exists.

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:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:L/VA:N/SC:L/SI:L/SA:N

Affected products

Mlflow · Mlflow

public PoCs found — 1

cve_referenceafine.com/blogs/attacking-mlflow-how-ml-artifacts-become-attack-vectorsunverified

⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.

Want to know if your infrastructure is exposed to this?

Talk to TrueHacking →

References

https://afine.com/blogs/attacking-mlflow-how-ml-artifacts-become-attack-vectors https://cert.pl/en/posts/2026/04/CVE-2026-33865/https://github.com/mlflow/mlflow/pull/21435