CVE-2026-2393

HIGHNVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under NVD CVSS v3. EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Elevated
7.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.1Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 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.

CVSS v3
7.1
EG Score
7.1(medium)
EPSS
20.6%
KEV
Not listed

Published

May 11, 2026

Last Modified

May 27, 2026

Advisory Details (2)

Auto-updated May 11, 2026
No patch confirmed yet.
generic

huntr - The world’s first bug bounty platform for AI/ML

https://huntr.com/bounties/04ef100d-06b5-4a70-95b1-b7be23aa8150
generic

Validate webhook url to fix SSRF vulnerability (#20747) · mlflow/mlflow@64aa0ab · GitHub

https://github.com/mlflow/mlflow/commit/64aa0ab7207f9c649b59ba1a5f40d82196817389

Vendor Advisories for CVE-2026-2393(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
mlflow0.0.1 ... 3.9.0rc0 (169 versions)3.9.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 51× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 123 total refreshes for this CVE.

  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-09 19:10 UTCEPSS rescore
  3. 2026-07-08 15:15 UTCEPSS rescore
  4. 2026-07-07 13:46 UTCEPSS rescore
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 16:27 UTCEPSS rescore
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 02:30 UTCEPSS rescore
  10. 2026-07-01 15:06 UTCEPSS rescore
  11. 2026-06-30 23:22 UTCEPSS rescore
  12. 2026-06-29 14:06 UTCEPSS rescore
  13. 2026-06-29 14:06 UTCEPSS rescore
  14. 2026-06-28 14:07 UTCEPSS rescore
  15. 2026-06-28 14:07 UTCEPSS rescore
  16. 2026-06-28 04:56 UTCEPSS rescore
  17. 2026-06-28 04:56 UTCEPSS rescore
  18. 2026-06-28 03:24 UTCEG score recompute
  19. 2026-06-27 09:53 UTCEG score recompute
  20. 2026-06-27 03:08 UTCEPSS rescore
  21. 2026-06-26 21:06 UTCEG score recompute
  22. 2026-06-26 05:07 UTCEG score recompute
  23. 2026-06-25 13:49 UTCEPSS rescore
  24. 2026-06-25 13:49 UTCEPSS rescore
  25. 2026-06-24 14:05 UTCEPSS rescore
Show 75 more
  1. 2026-06-23 21:33 UTCEPSS rescore
  2. 2026-06-23 21:33 UTCEPSS rescore
  3. 2026-06-22 14:25 UTCEPSS rescore
  4. 2026-06-22 14:25 UTCEPSS rescore
  5. 2026-06-21 14:56 UTCEPSS rescore
  6. 2026-06-21 14:56 UTCEPSS rescore
  7. 2026-06-21 01:59 UTCEPSS rescore
  8. 2026-06-21 01:59 UTCEPSS rescore
  9. 2026-06-19 19:25 UTCEPSS rescore
  10. 2026-06-19 19:25 UTCEPSS rescore
  11. 2026-06-18 17:52 UTCEPSS rescore
  12. 2026-06-17 17:53 UTCEPSS rescore
  13. 2026-06-17 17:53 UTCEPSS rescore
  14. 2026-06-17 01:00 UTCEG score recompute
  15. 2026-06-16 17:52 UTCEPSS rescore
  16. 2026-06-16 07:26 UTCEG score recompute
  17. 2026-06-15 17:48 UTCEPSS rescore
  18. 2026-06-15 02:33 UTCEG score recompute
  19. 2026-06-14 23:18 UTCEPSS rescore
  20. 2026-06-14 14:34 UTCEG score recompute
  21. 2026-06-14 01:56 UTCEG score recompute
  22. 2026-06-13 23:00 UTCEPSS rescore
  23. 2026-06-12 23:12 UTCEPSS rescore
  24. 2026-06-12 23:12 UTCEPSS rescore
  25. 2026-06-12 22:43 UTCEG score recompute
  26. 2026-06-12 10:37 UTCEG score recompute
  27. 2026-06-11 22:37 UTCEG score recompute
  28. 2026-06-11 14:00 UTCEPSS rescore
  29. 2026-06-11 10:39 UTCEG score recompute
  30. 2026-06-10 22:33 UTCEG score recompute
  31. 2026-06-10 22:18 UTCEPSS rescore
  32. 2026-06-10 22:18 UTCEPSS rescore
  33. 2026-06-10 13:22 UTCEPSS rescore
  34. 2026-06-10 10:34 UTCEG score recompute
  35. 2026-06-09 22:34 UTCEG score recompute
  36. 2026-06-09 08:26 UTCEG score recompute
  37. 2026-06-08 20:26 UTCEG score recompute
  38. 2026-06-08 14:17 UTCEPSS rescore
  39. 2026-06-08 14:17 UTCEPSS rescore
  40. 2026-06-08 06:55 UTCEG score recompute
  41. 2026-06-07 18:56 UTCEG score recompute
  42. 2026-06-07 15:25 UTCEPSS rescore
  43. 2026-06-07 15:25 UTCEPSS rescore
  44. 2026-06-07 15:25 UTCEPSS rescore
  45. 2026-06-07 06:57 UTCEG score recompute
  46. 2026-06-06 18:58 UTCEG score recompute
  47. 2026-06-06 13:47 UTCEPSS rescore
  48. 2026-06-06 13:47 UTCEPSS rescore
  49. 2026-06-06 06:59 UTCEG score recompute
  50. 2026-06-05 22:47 UTCEPSS rescore
  51. 2026-06-05 22:47 UTCEPSS rescore
  52. 2026-06-05 19:00 UTCEG score recompute
  53. 2026-06-05 07:01 UTCEG score recompute
  54. 2026-06-05 06:10 UTCEPSS rescore
  55. 2026-06-05 06:10 UTCEPSS rescore
  56. 2026-06-04 19:02 UTCEG score recompute
  57. 2026-06-04 13:12 UTCEPSS rescore
  58. 2026-06-04 13:12 UTCEPSS rescore
  59. 2026-06-04 07:03 UTCEG score recompute
  60. 2026-06-03 19:04 UTCEG score recompute
  61. 2026-06-03 07:04 UTCEG score recompute
  62. 2026-06-02 20:13 UTCEPSS rescore
  63. 2026-06-02 20:13 UTCEPSS rescore
  64. 2026-06-02 19:05 UTCEG score recompute
  65. 2026-06-02 07:06 UTCEG score recompute
  66. 2026-06-01 19:06 UTCEG score recompute
  67. 2026-06-01 13:51 UTCEPSS rescore
  68. 2026-06-01 13:51 UTCEPSS rescore
  69. 2026-06-01 07:03 UTCEG score recompute
  70. 2026-05-31 22:30 UTCEPSS rescore
  71. 2026-05-31 22:30 UTCEPSS rescore
  72. 2026-05-31 00:16 UTCEPSS rescore
  73. 2026-05-31 00:16 UTCEPSS rescore
  74. 2026-05-29 13:44 UTCEPSS rescore
  75. 2026-05-29 13:44 UTCEPSS rescore

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-2393?
CVE-2026-2393 is a high vulnerability published on May 11, 2026. A Server-Side Request Forgery (SSRF) vulnerability exists in MLflow versions prior to 3.9.0. The createwebhook() function in mlflow/server/handlers.py accepts a user-controlled url parameter without validation, and the sendwebhook_request() function in mlflow/webhooks/delivery.py sends HTTP POST…
When was CVE-2026-2393 disclosed?
CVE-2026-2393 was first published in the National Vulnerability Database on May 11, 2026, with the most recent update on May 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-2393 actively exploited?
CVE-2026-2393 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-2393?
CVE-2026-2393 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-2393?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-2393, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-2393

Explore →

Is Your Infrastructure Affected by CVE-2026-2393?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs