CVE-2026-79721: Code execution can occur in versions of the MLflow platform running version 0.0.1 or newer, enabling a maliciously crafted model artifact to…
Noroxi assessment
Priority: Monitor (action score 34/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.47% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
Code execution can occur in versions of the MLflow platform running version 0.0.1 or newer, enabling a maliciously crafted model artifact to execute arbitrary code on an end user's system when loaded by the project.
- Published
- Sep 8, 2026
- Updated
- Sep 9, 2026
- EPSS
- 0.4% · 41th percentile
- CWE
- CWE-829
Report tools
Action score
34
Low priority for now.
- CVSS
- 34 / 40 · 8.6 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.4%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- —
- CNA · HiddenLayer
- 8.6
- NVD has not scored this yet; the score shown is the CNA’s.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Is your version affected? Check itNoroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
—
Versions reported by the vendor
Affected version ranges reported by the assigning authority (HiddenLayer). Independent of NVD's CPE analysis and usually ahead of it.
mlflow mlflow
- 0.0.1 and lateraffected · semver
Same product
mlflow: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-116692MLflow: Remote code execution on unauthenticated MLflow servers via third-party scorer deserialization importing caller-placed artifact modules39Monitor
- CVE-2026-53995MLflow 3.17.1 and prior Path Traversal via Trace ID API35Monitor
- CVE-2026-96804MLflow's statsmodel flavor, versions 2.1.0 to 3.14.0, omits the MLFLOW_ALLOW_PICKLE_DESERIALIZATION=False security control entirely in…35Monitor
Published before and after this one in the same product
- ← EarlierCVE-2026-69146Aug 17, 2026 · MLflow: LogInputs endpoint bypasses per-run UPDATE authorization in basic-auth26Monitor
- ← EarlierCVE-2026-69148Aug 17, 2026 · MLflow: CreateModelVersion source validation does not check READ permission on referenced run_id28Monitor
- Later →CVE-2026-96775Sep 23, 2026 · MLflow dspy bypasses pickle deserialization control35Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Not on record for this CVE: patch commit or PR link · researcher credit · variant or chain candidate · public bounty program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- Integrity
- Availability
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- P
- Scope
- X
Weakness class (CWE)
CWE-829 · Inclusion of Functionality from Untrusted Control SphereCVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
- Code InclusionCAPEC-175likelihood: Medium · Very High
- Serialized Data External LinkingCAPEC-201likelihood: High · High
- DTD InjectionCAPEC-228Medium
- Local Code InclusionCAPEC-251Medium
- PHP Local File InclusionCAPEC-252Medium
- Remote Code InclusionCAPEC-253
- Force Use of Corrupted FilesCAPEC-263Medium
- Open-Source Library ManipulationCAPEC-538likelihood: Low · High
ATT&CK techniques
- Process InjectionT1055
- Browser ExtensionsT1176
- Supply Chain Compromise: Software Dependencies and Development ToolsT1195.001
- Server Software Component: IIS ComponentsT1505.004
- Server Software Component: Terminal Services DLLT1505.005
- Hijack Execution Flow: Dynamic Linker HijackingT1574.006
- Hijack Execution Flow: KernelCallbackTableT1574.013
- Reflective Code LoadingT1620
Change log (0)
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.