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 — 3 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: 9.8%CVSS: 9.3Exploit: cisa kev · ssvc active · epss top5pct · public exploitExposed services: Not assessed

A fix is available — apply it.

MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. Starting in 3.3.0 and 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.3CRITICALhigh confidence
EG Risk
97
EG Risk 97/100CISA SSVC

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%
CISA SSVC: Attend at low or medium mission impact; Act at high (mission-essential systems).
Action: A fix is available. Apply it sooner than your standard update timelines at low or medium mission impact and as soon as possible at high.
EPSS PROB
9.8%
EPSS %ILE
95th
KEV
⚠ Exploited

CISA SSVCAttend at low or medium mission impact; Act at high (mission-essential systems).

A fix is available. Apply it sooner than your standard update timelines at low or medium mission impact and as soon as possible at high.

Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 17, 2026

Last Modified

October 5, 2026

Advisory Details (6)

Auto-updated Oct 2, 2026
⚠️ Active exploitation confirmed. Patch available. Sources: github_commit, github_pr, github_release, github, cisa.
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(3)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-mlflow-rhel9:17872267902026-08-27redhat
redhatrhoai/odh-latency-predictor-training-rhel9:17865522502026-08-26redhat

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 rangeFix by version rangeDependents
mlflow0.0.1 ... 3.9.0rc0 (182 versions)
  • 3.3.0 up to 3.15.0: fixed in 3.15.0
  • every version up to 3.15.0: fixed in 3.15.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 55× in last 7d / 230× 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 333 total refreshes for this CVE.

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

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 ↗

Related CVEs(same product + same vendor + same CWE)

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. Starting in 3.3.0 and 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…
When was CVE-2026-64849 disclosed?
CVE-2026-64849 was first published on August 17, 2026, with the most recent update on October 5, 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 attention. A fix is available. Apply it.
What is the CVSS score of CVE-2026-64849?
CVE-2026-64849 has a CVSS base score of 9.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
Which products are affected by CVE-2026-64849?
CVE-2026-64849 affects MLflow MLflow. The affected packages EchelonGraph has on record, with version ranges, are listed in the Affected Packages section of this page.
How do I remediate CVE-2026-64849?
A fix for CVE-2026-64849 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-64849 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs