Vulnerability · CVE-2026-2393
A Server-Side Request Forgery (SSRF) vulnerability exists in MLflow versions prior to 3.9.0.
Published May 11, 2026 · catalog updated Jun 17, 2026 · A Server-Side Request Forgery
Check if you run it
No confirmed exploitation is on record for CVE-2026-2393. EPSS is 0.29%. Act only if a listed version of A Server-Side Request Forgery is installed.
Gaps on this record
- The stored product name is a package slug. The name on this page is taken from the title (A Server-Side Request Forgery).
- No version range is stored. A customer cannot check an installed version against this record.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- High7.1
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.29%
- Remediation
- Advisory link
- Affected products
- cpe lfprojects/mlflow
A Server-Side Request Forgery (SSRF) vulnerability exists in MLflow versions prior to 3.9.0. The function in accepts a user-controlled parameter without validation, and the function in sends HTTP POST requests to this attacker-controlled URL. This allows an authenticated attacker to force the MLflow backend to send HTTP requests to internal services, cloud metadata endpoints, or arbitrary external servers. The lack of input sanitization, URL scheme filtering, or allowlist validation on the webhook URL enables exploitation, potentially leading to cloud credential theft, internal network access, and data exfiltration.
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe lfprojects/mlflowversion unspecified
How to fix CVE-2026-2393
Recommended remediation
A patch or advisory reference is linked. Open the original publisher for availability by product version.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2026-2393. EPSS is 0.29%. Act only if a listed version of A Server-Side Request Forgery is installed.
Which versions are affected?
Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-918: Server-Side Request Forgery (SSRF). EPSS 0.29%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
May 11, 2026 · NIST NVD
Detected
A Server-Side Request Forgery (SSRF) vulnerability exists in MLflow versions prior to 3.9.0. The function in accepts a user-controlled parameter without validation, and the function in sends HTTP POST requests to this attacker-controlled URL. This allows an authenticated attacker to force the MLflow backend to send HTTP requests to internal services, cloud metadata endpoints, or arbitrary external
Jun 17, 2026 · NIST NVD
Updated
A Server-Side Request Forgery (SSRF) vulnerability exists in MLflow versions prior to 3.9.0. The function in accepts a user-controlled parameter without validation, and the function in sends HTTP POST requests to this attacker-controlled URL. This allows an authenticated attacker to force the MLflow backend to send HTTP requests to internal services, cloud metadata endpoints, or arbitrary external
Sources
- CVE.orgVulnerability recordCVE-2026-2393
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2026-2393
30-day exploitation probability 0.3%
first.org - NIST NVDVulnerability recordCVE-2026-2393
A Server-Side Request Forgery (SSRF) vulnerability exists in MLflow versions prior to 3.9.0. The function in accepts a user-controlled parameter without validation, and the function in `mlflow/webhook
nvd.nist.gov
References
Freshness
Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.