Stored XSS via executable YAML function tags
Published Apr 7, 2026 · Updated Apr 7, 2026
Stored XSS in the MLflow web UI through 3.10.1 allows remote authenticated users to execute JavaScript when a victim views an MLmodel artifact. The logged-model artifact viewer passes attacker-controlled YAML to js-yaml's unsafe load(), which instantiates !!js/function objects and invokes a crafted signature.inputs toString during JSON parsing. The attacker needs artifact-upload access and another user's interaction with the logged-model view; execution occurs in that user's browser session.
Summary
What happened
Stored XSS in the MLflow web UI through 3.10.1 allows remote authenticated users to execute JavaScript when a victim views an MLmodel artifact. The logged-model artifact viewer passes attacker-controlled YAML to js-yaml's unsafe load(), which instantiates !!js/function objects and invokes a crafted signature.inputs toString during JSON parsing. The attacker needs artifact-upload access and another user's interaction with the logged-model view; execution occurs in that user's browser session.
The record
- CVE
- CVE-2026-33865
- Published
- Apr 7, 2026
- Updated
- Apr 7, 2026
- Vendor
- MLflow Project
- Product
- MLflow
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Apr 7, 2026CVE publishedPublication date reported by the CVE source.
- Apr 7, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=3.10.1
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- AFINE MLflow stored-XSS proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo