CVE-2026-64849

CRITICALPre-NVD 9.39.3
EchelonGraph scoreHIGH confidence

“—” beside the score: it is equal to the CVSS score beside it.

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 Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, a secondary CVSS source
Exploited in the wild

Also known asEUVD-2026-60473 (ENISA EUVD) · GHSA-7gwp-5pfp-969j (GitHub Security Advisories) · PYSEC-2026-3687 (OSV.dev)Source: ENISA EUVD

9.3EG
EchelonGraph verdictPatch nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 11%CVSS: 9.3Exploit: No code on recordExposed 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 POST /api/2.0/mlflow/webhooks/{id}/test endpoint (accessible without credentials when server authentication is not enabled) 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. The unauthenticated attack scenario described here applies to deployments without authentication. With MLflow’s built-in basic authentication enabled, requests to this endpoint require valid credentials; this issue does not itself bypass authentication. This issue is fixed in version 3.15.0.

CVSS v3
9.3
EG Score
9.3CRITICALhigh confidence
EG Risk
97
EG Risk 97/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity93% × 45%
Impact severity (EG Severity): CVSS 9.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Attend at low or medium mission impact; Act at high (mission-essential systems).
Exploitation active (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
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
11%
EPSS %ILE
95th
KEV
⚠ Exploited

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (9.3): severity, escalated by confirmed exploitation. This CVE's 9.3 is its impact severity (EG Severity), not escalated.

EG Severity
9.3 CRITICALCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.GitHub Security Advisory CVSS
EG Likelihood
11% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-11-21). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
CISA KEV and EG-KEV Tier 1 (exploited in the wild)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Attend at medium mission impactAttend at low or medium mission impact; Act at high (mission-essential systems).CISA BOD 26-04: 3 days if the affected system is publicly exposed; 14 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Attend 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). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days if the affected system is publicly exposed; 14 days if it is not.

The score's inputs: In CISA KEV yes (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://github.com/mlflow/mlflow/pull/24258 · https://github.com/mlflow/mlflow/issues/24179 · https://www.cisa.gov/news-events/directives/bod-26-04-prioritizing-security-updates-based-risk · https://www.cisa.gov/news-events/directives/bod-26-04-implementation-guidance-prioritizing-security-updates-based-risk · https://nvd.nist.gov/vuln/detail/CVE-2026-64849

Published

August 17, 2026

Last Modified

November 20, 2026

Advisory Details (6)

Auto-updated Nov 19, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Patch available. Sources: cisa, github, github_commit, github_pr, github_release.
CISA🔴 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 advisoryMentions a patch (unverified)🟡 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 pull request

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
Web page

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 and National Authority Advisories for CVE-2026-64849(4)

These vendors and national cybersecurity authorities published their own advisory mentioning this CVE — often with remediation steps + affected product lists not in NVD. An authority's is an excerpt, in the language it published it in, not translated, and credited to it with a link.

Patch Availability(3)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatrhoai/odh-mlflow-rhel9:17872267902026-08-27redhat
redhatrhoai/odh-latency-predictor-training-rhel9:17865522502026-08-26redhat
pipmlflow @ 3.15.0 (fixes >= 3.3.0, < 3.15.0)—ghsa

These rows come from Red Hat and GitHub (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 24× in last 7d / 81× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.

Showing the most recent 100 of 534 rows on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 434 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-22 16:43 UTCEchelonGraph re-scored
  2. 2026-11-22 16:43 UTCVendor advisory
  3. 2026-11-22 16:43 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  4. 2026-11-21 16:40 UTCEPSS rescoreEPSS 11% · 95th percentile
  5. 2026-11-21 15:44 UTCEchelonGraph re-scored
  6. 2026-11-21 15:44 UTCVendor advisory
  7. 2026-11-21 15:44 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  8. 2026-11-20 16:38 UTCEPSS rescoreEPSS 11% · 95th percentile
  9. 2026-11-20 14:48 UTCVendor advisory
  10. 2026-11-20 14:48 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  11. 2026-11-19 22:29 UTCEchelonGraph re-scored
  12. 2026-11-19 22:29 UTCVendor advisory
  13. 2026-11-19 22:28 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  14. 2026-11-19 21:24 UTCEchelonGraph re-scored
  15. 2026-11-19 21:24 UTCVendor advisory
  16. 2026-11-19 21:24 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  17. 2026-11-19 16:35 UTCEPSS rescoreEPSS 10% · 95th percentile
  18. 2026-11-19 11:15 UTCEchelonGraph re-scored
  19. 2026-11-19 11:15 UTCVendor advisory
  20. 2026-11-19 11:15 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  21. 2026-11-18 16:35 UTCEPSS rescoreEPSS 10% · 95th percentile
  22. 2026-11-18 10:19 UTCEchelonGraph re-scored
  23. 2026-11-18 10:19 UTCVendor advisory
  24. 2026-11-18 10:19 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  25. 2026-11-17 16:35 UTCEPSS rescoreEPSS 10% · 95th percentile
Show 75 more
  1. 2026-11-17 09:19 UTCEchelonGraph re-scored
  2. 2026-11-17 09:19 UTCVendor advisory
  3. 2026-11-17 09:19 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  4. 2026-11-16 16:52 UTCEPSS rescoreEPSS 10% · 95th percentile
  5. 2026-11-16 08:23 UTCEchelonGraph re-scored
  6. 2026-11-16 08:23 UTCVendor advisory
  7. 2026-11-16 08:23 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  8. 2026-11-15 17:01 UTCEPSS rescoreEPSS 10% · 95th percentile
  9. 2026-11-15 07:26 UTCEchelonGraph re-scored
  10. 2026-11-15 07:26 UTCVendor advisory
  11. 2026-11-15 07:26 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  12. 2026-11-14 16:41 UTCEPSS rescoreEPSS 10% · 95th percentile
  13. 2026-11-14 06:30 UTCEchelonGraph re-scored
  14. 2026-11-14 06:30 UTCVendor advisory
  15. 2026-11-14 06:30 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  16. 2026-11-13 16:53 UTCEPSS rescoreEPSS 10% · 95th percentile
  17. 2026-11-13 05:24 UTCEchelonGraph re-scored
  18. 2026-11-13 05:24 UTCVendor advisory
  19. 2026-11-13 05:24 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  20. 2026-11-12 16:34 UTCEPSS rescoreEPSS 10% · 95th percentile
  21. 2026-11-12 04:28 UTCEchelonGraph re-scored
  22. 2026-11-12 04:28 UTCVendor advisory
  23. 2026-11-12 04:28 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  24. 2026-11-11 16:40 UTCEPSS rescoreEPSS 10% · 95th percentile
  25. 2026-11-11 03:31 UTCEchelonGraph re-scored
  26. 2026-11-11 03:31 UTCVendor advisory
  27. 2026-11-11 03:31 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  28. 2026-11-10 16:45 UTCEPSS rescoreEPSS 10% · 95th percentile
  29. 2026-11-10 02:34 UTCEchelonGraph re-scored
  30. 2026-11-10 02:34 UTCVendor advisory
  31. 2026-11-10 02:34 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  32. 2026-11-09 01:38 UTCEchelonGraph re-scored
  33. 2026-11-09 01:38 UTCVendor advisory
  34. 2026-11-09 01:38 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  35. 2026-11-08 16:40 UTCEPSS rescoreEPSS 10% · 95th percentile
  36. 2026-11-08 00:42 UTCEchelonGraph re-scored
  37. 2026-11-08 00:42 UTCVendor advisory
  38. 2026-11-08 00:42 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  39. 2026-11-07 16:39 UTCEPSS rescoreEPSS 10% · 95th percentile
  40. 2026-11-06 23:47 UTCEchelonGraph re-scored
  41. 2026-11-06 23:47 UTCVendor advisory
  42. 2026-11-06 23:47 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  43. 2026-11-06 16:39 UTCEPSS rescoreEPSS 10% · 95th percentile
  44. 2026-11-06 15:25 UTCOSV refresh
  45. 2026-11-05 22:50 UTCEchelonGraph re-scored
  46. 2026-11-05 22:50 UTCVendor advisory
  47. 2026-11-05 22:50 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  48. 2026-11-05 16:38 UTCEPSS rescoreEPSS 10% · 95th percentile
  49. 2026-11-04 21:54 UTCEchelonGraph re-scored
  50. 2026-11-04 21:54 UTCVendor advisory
  51. 2026-11-04 21:54 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  52. 2026-11-04 16:36 UTCEPSS rescoreEPSS 10% · 95th percentile
  53. 2026-11-03 20:57 UTCEchelonGraph re-scored
  54. 2026-11-03 20:57 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  55. 2026-11-03 16:48 UTCEPSS rescoreEPSS 10% · 95th percentile
  56. 2026-11-02 20:01 UTCEchelonGraph re-scored
  57. 2026-11-02 20:01 UTCVendor advisory
  58. 2026-11-02 20:01 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  59. 2026-11-01 19:05 UTCEchelonGraph re-scored
  60. 2026-11-01 19:05 UTCVendor advisory
  61. 2026-11-01 19:05 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  62. 2026-11-01 16:35 UTCEPSS rescoreEPSS 10% · 95th percentile
  63. 2026-11-01 07:40 UTCGHSA enrichmentGHSA-7gwp-5pfp-969j · GitHub severity CRITICAL · GitHub CVSS 9.3
  64. 2026-11-01 07:40 UTCEchelonGraph re-scored
  65. 2026-10-31 18:08 UTCEchelonGraph re-scored
  66. 2026-10-31 18:08 UTCVendor advisory
  67. 2026-10-31 16:33 UTCEPSS rescoreEPSS 10% · 95th percentile
  68. 2026-10-30 17:11 UTCEchelonGraph re-scored
  69. 2026-10-30 17:11 UTCVendor advisory
  70. 2026-10-30 16:35 UTCEPSS rescoreEPSS 10% · 95th percentile
  71. 2026-10-29 16:33 UTCEPSS rescoreEPSS 10% · 95th percentile
  72. 2026-10-29 16:15 UTCEchelonGraph re-scored
  73. 2026-10-29 16:15 UTCVendor advisory
  74. 2026-10-28 16:33 UTCEPSS rescoreEPSS 10% · 95th percentile
  75. 2026-10-28 15:18 UTCEchelonGraph re-scored

Public detection templates

(1 reference)

A public Nuclei detection template is referenced for this CVE. A detection template checks whether a system is affected; it is not necessarily exploit code.

  • Nucleihttp/cves/2026/CVE-2026-64849.yaml
    Published Aug 18, 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-severity vulnerability; its CVE record was 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 POST /api/2.0/mlflow/webhooks/{id}/test endpoint (accessible without credentials when server authentication is not enabled) calls…
When was the CVE record for CVE-2026-64849 published?
The CVE record for CVE-2026-64849 was published on August 17, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of November 20, 2026; the record at its source may have been updated since.
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 and National Authority Advisories panel on this page. NCSC-NL's advisory for CVE-2026-64849 is also listed there, in Dutch, as NCSC-NL published it; not translated.

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.