Advisory record · GHSA-pgqp-8h46-6x4j

MLFlow is vulnerable to DNS rebinding attacks due to a lack of Origin header validation

CVSS 8.1 HighEPSS 0.0022 · 12th percentile

Published by the GitHub Advisory Database at 12 Jan 2026, 09:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
mlflowPyPI<3.5.03.5.0
Identifiers
GHSA-pgqp-8h46-6x4j · BIT-mlflow-2025-14279 · CVE-2025-14279 · PYSEC-2026-1656
Weakness (CWE)
CWE-346
Published
12 Jan 2026
Updated
10 Sept 2026

Machine-written summary

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

MLflow versions before 3.5.0 are vulnerable to DNS rebinding attacks because the REST server does not validate the Origin header. An attacker who lures a user to a malicious website can make unauthorized calls to REST endpoints to query, update, or delete experiments. Upgrade mlflow to version 3.5.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
8.1 High 3.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N CNA (@huntr_ai)
  • CISA KEV Not listed.
  • EPSS 0.0022, the 12th percentile, on 10 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:34 UTC First seen by agentprime
  2. 31 Oct 2026, 14:34 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.