CVE-2026-2393: A Server-Side Request Forgery (SSRF) vulnerability exists in MLflow versions prior to 3.9.0

Q: How do I fix CVE-2026-2393?

mlflow: upgrade to 3.9.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-2393 being exploited?

CVE-2026-2393 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-2393 affect?

CVE-2026-2393 affects mlflow. Severity is high (CVSS 7.1). 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` parameter without validation, and the `_send_webhoo

Q: How urgent is CVE-2026-2393?

Priority 35/100. High severity; Public exploit reference

Routine

HIGH 7.1UPGRADE

CVE-2026-2393 is a high-severity flaw (CVSS 7.1) affecting mlflow. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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` parameter without validation, and the `_send_webhook_request()` function in `mlflow/webhooks/delivery.py` sends HTTP POST requests to this attacker-controlled URL. This allows an authenticated attacker to force the MLflow backend to send HTTP requests to intern

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	7.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 79%)
CISA exploited list	No
Weakness	CWE-918
Published	2026-05-11
Last modified	2026-06-17

Publisher (CNA): huntr.dev · Vendor: lfprojects

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-11 18:16 UTCPublished CVE record published
2026-06-17 10:30 UTCUpdated Record last modified

lfprojects mlflow UPGRADE

Affected: < 3.9.0

Fixed in: 3.9.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy mlflow || rpm -q mlflow || mlflow --version

2. UPGRADE to 3.9.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade mlflow

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade mlflow

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-2393?

mlflow: upgrade to 3.9.0. Exact commands for each OS are on this page.

Is CVE-2026-2393 being exploited?

CVE-2026-2393 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-2393 affect?

CVE-2026-2393 affects mlflow. Severity is high (CVSS 7.1). 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` parameter without validation, and the `_send_webhoo

How urgent is CVE-2026-2393?

Priority 35/100. High severity; Public exploit reference

Related CVEs

CVE-2026-64849 CRITICAL 9.3 EXPLOITED UPGRADE MLflow Server-Side Request Forgery Vulnerability
CVE-2026-8147 HIGH 8.1 UPGRADE In MLflow versions prior to 3.14.0, when running with authentication enabled, the trace API endpoints lack pro
CVE-2026-2611 CRITICAL 9.6 UPGRADE In MLflow version 3.9.0, the MLflow Assistant feature introduced improper origin validation in its /ajax-api e
CVE-2026-2614 HIGH 7.5 UPGRADE A vulnerability in the `_create_model_version()` handler of `mlflow/server/handlers.py` in mlflow/mlflow versi
CVE-2026-4035 HIGH 7.7 UPGRADE A vulnerability in mlflow/mlflow versions prior to 3.11.0 allows for the resolution of environment variables i

References

← Back to latest CVEs