Advisory record · GHSA-65h7-c7c4-mghx

A Server-Side Request Forgery (SSRF) vulnerability exists in MLflow versions prior to 3.9.0. The `_create_webhook()` function in `mlflow/server/handlers.py` accepts a user-controlled `url` paramete...

CVSS 7.1 HighEPSS 0.0029 · 21st percentile

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

PackageEcosystemAffectedFixed in
mlflowPyPI<3.9.03.9.0
Identifiers
GHSA-65h7-c7c4-mghx · BIT-mlflow-2026-2393 · CVE-2026-2393 · PYSEC-2026-2219
Weakness (CWE)
CWE-918
Published
11 May 2026
Updated
13 Jul 2026

Machine-written summary

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

MLflow versions prior to 3.9.0 are vulnerable to server-side request forgery through webhook creation, where the webhook URL is accepted without validation. An authenticated attacker can make the MLflow backend send HTTP POST requests to internal services, cloud metadata endpoints, or external servers, potentially enabling credential theft or data exfiltration. Upgrade to MLflow 3.9.0 or later.

Written 5 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
7.1 High 3.0 CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N CNA (@huntr_ai)
  • CISA KEV Not listed.
  • EPSS 0.0029, the 21st percentile, on 14 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 11 May 2026, 18:16 UTC Confirmed by NVD
  2. 31 Oct 2026, 14:43 UTC First seen by agentprime
  3. 31 Oct 2026, 14:43 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.