Advisory record · GHSA-59v3-898r-qwhj

MLflow Server-Side Request Forgery (SSRF)

CVSS 8.6 HighEPSS 0.015 · 74th percentile

Published by the GitHub Advisory Database at 29 Jun 2026, 11:50 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
mlflowPyPI<2.9.22.9.2
Identifiers
GHSA-59v3-898r-qwhj · BIT-mlflow-2023-6974 · CVE-2023-6974 · PYSEC-2026-416
Weakness (CWE)
CWE-918
Published
29 Jun 2026
Updated
1 Jul 2026

Machine-written summary

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

MLflow versions before 2.9.2 are vulnerable to server-side request forgery. An attacker with access to the MLflow server can make it send requests to internal HTTP(s) servers, and the source says this could in the worst case lead to remote code execution on the host, for example on an AWS instance. Upgrade mlflow to version 2.9.2 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
8.6 High 3.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N CNA (@huntr_ai)
  • CISA KEV Not listed.
  • EPSS 0.015, the 74th percentile, on 13 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

This record came from the full history of the GitHub Advisory Database, published 29 Jun 2026. New records show when each source confirmed them.

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.