CVE-2026-64849

CRITICALPre-NVD 9.39.3—
EchelonGraph scoreHIGH confidence

Score elevated to 9.3 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2026-08-19), indicating real-world exploitation has been confirmed by US federal agencies. a secondary CVSS source baseline 9.3 retained for reference (NVD's own analysis pending). Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: cisa_kev, epss, secondary
Trending — 4 sources updated this weekExploited in the wild
9.3EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV)
CISA-KEV: ExploitedEPSS PROB: 16%CVSS: 9.3Exploit: cisa kev · ssvc active · epss top5pct · public exploitExposed: 0

A fix is available — apply it.

MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. Prior to 3.15.0, the unauthenticated POST /api/2.0/mlflow/webhooks/{id}/test endpoint calls _validate_webhook_url() in mlflow/utils/validation.py only for the original URL while mlflow/webhooks/delivery.py follows redirects and re-resolves the hostname without pinning the validated address, allowing attackers to reach internal or cloud metadata services and receive response_status and response_body. This issue is fixed in version 3.15.0.

CVSS v3
9.3
EG Score
9.3(high)
EG Risk
97(Attend)
EG Risk 97/100SSVC: Attend

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity93% × 45%
Exploitation100% × 40%
Automatability100% × 15%
Action: Remediate soon — notable exploitation risk.
EPSS PROB
16%
EPSS %ILE
97%
KEV
⚠ Exploited

Published

August 17, 2026

Last Modified

August 20, 2026

Advisory Details (6)

Auto-updated Sep 15, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: github_pr, github_release, github, cisa, github_commit.
cisa Patch Available🔴 Active Exploitation

Known Exploited Vulnerabilities Catalog | CISA

Known Exploited Vulnerabilities Catalog | CISA. Listed in CISA Known Exploited Vulnerabilities catalog.

https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-64849
github Patch Available🟡 PoC Available

Unauthenticated full-read SSRF in MLflow webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebinding) · Advisory · mlflow/mlflow · GitHub

https://github.com/mlflow/mlflow/security/advisories/GHSA-7gwp-5pfp-969j
github_release Patch Available

v3.15.0

Patch available: mlflow/mlflow v3.15.0

https://github.com/mlflow/mlflow/releases/tag/v3.15.0
github_pr

Fix DNS-rebinding SSRF bypass in webhook delivery

Fix merged in mlflow/mlflow PR #24258 on 2026-07-02 — awaiting tagged release

https://github.com/mlflow/mlflow/pull/24258
generic

DNS rebinding bypass of webhook SSRF protection enables cloud metadata access · Issue #24179 · mlflow/mlflow · GitHub

https://github.com/mlflow/mlflow/issues/24179
github_commit

commit ba949522477c (mlflow/mlflow)

Fix landed in mlflow/mlflow commit ba949522477c — awaiting tagged release

https://github.com/mlflow/mlflow/commit/ba949522477cbd5915aa55d29b0cfad7d5ddf939

Vendor Advisories for CVE-2026-64849(2)

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatrhoai/odh-mlflow-rhel9:17872267902026-08-27redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 53× in last 7d / 191× 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 208 total refreshes for this CVE.

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

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-64849.yaml
    First seen Jan 1, 2026

    MLflow Webhook SSRF - Unauthenticated Full-Read via Redirect Bypass

    Open source ↗

Frequently asked(6)

What is CVE-2026-64849?
CVE-2026-64849 is a critical vulnerability published on August 17, 2026. MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. Prior to 3.15.0, the unauthenticated POST /api/2.0/mlflow/webhooks/{id}/test endpoint calls validatewebhookurl() in mlflow/utils/validation.py only for the original URL while…
When was CVE-2026-64849 disclosed?
CVE-2026-64849 was first published in the National Vulnerability Database on August 17, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-64849 actively exploited?
Yes. CISA added CVE-2026-64849 to the Known Exploited Vulnerabilities catalog on August 19, 2026, affecting MLflow MLflow. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate patching attention.
What is the CVSS score of CVE-2026-64849?
CVE-2026-64849 has a CVSS v3 base score of 9.3 (NVD).
Which products are affected by CVE-2026-64849?
CVE-2026-64849 affects MLflow MLflow. The full affected-products list, including version ranges and fixed versions, is shown in the Affected Packages section of this page.
How do I remediate CVE-2026-64849?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-64849, 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-64849

Explore →

Is Your Infrastructure Affected by CVE-2026-64849?

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

Start Free Scan →Browse All CVEs