Advisory record · GHSA-f798-qm4r-23r5

MLflow allowed arbitrary files to be PUT onto the server

CVSS 10.0 CriticalCriticalEPSS 0.049 · 92nd percentile

Critical, because:

  • CVSS score 10.0: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 16 Nov 2023, 18:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
mlflowPyPI<2.8.12.8.1
Identifiers
GHSA-f798-qm4r-23r5 · BIT-mlflow-2023-6015 · CVE-2023-6015 · PYSEC-2026-420
Weakness (CWE)
CWE-22
Published
16 Nov 2023
Updated
16 Nov 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

MLflow versions before 2.8.1 allowed arbitrary files to be PUT onto the server. The source gives few details about the required access or attack conditions. Upgrade mlflow to version 2.8.1 or later.

Written 10 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
10.0 Critical 3.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:N CNA (@huntr_ai)
  • CISA KEV Not listed.
  • EPSS 0.049, the 92nd percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 16 Nov 2023, 18:30 UTC Confirmed by GitHub Advisory Database
  2. 16 Nov 2026, 15:45 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.