# CVE-2026-64849: MLflow Tracking Server, is it exploitable where you run it

Ledger entry, disclosed 17 Aug 2026, sources read 19 Nov 2026

**The short answer.** CVE-2026-64849 affects MLflow Tracking Server and was disclosed 17 Aug 2026 with a CVSS score of 9.3. Exposure needs these conditions: MLflow is 3.3.0 to 3.14.x (3.15.x on IPv6 or NAT64) with a SQL store, the default; the webhooks API is open (no --app-name basic-auth) and the host can reach internal targets.

## What the flaw is

The MLflow Tracking Server has a model-registry webhooks API. A webhook is a URL the server calls when a registry event happens, and a test endpoint (POST /api/2.0/mlflow/webhooks/{id}/test) calls the URL on demand and returns the response status and body to the caller. MLflow checks the webhook URL against a rule that rejects non-public addresses, but it checks only the URL as first written. Delivery then follows HTTP redirects and looks up the hostname again, without pinning the address it checked.

An attacker points a webhook at a public HTTPS host they control. The host passes the check and then redirects to an internal address, or its DNS answer changes between the check and the call. The MLflow server fetches the internal target and the test endpoint hands the reply back. That reaches cloud instance metadata (which can hold temporary cloud credentials), internal admin services and internal ports. The advisory also describes a blind variant: redirect codes 307 and 308 keep the POST method and body, so an attacker can send POST requests to internal endpoints that act on POST.

The default mlflow server runs with no authentication, so no login is needed. The only webhook authorization lives in an optional auth plugin that is not loaded by default. The CNA rates it 9.3 (CVSS 3.1 base score, vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N: network, low complexity, no privileges, no user interaction, scope changed, high confidentiality impact, low integrity impact).

## Are you exposed: each condition and how to check it

| Condition for exposure | How to check it on your system |
| --- | --- |
| MLflow is 3.3.0 to 3.14.x (3.15.x on IPv6 or NAT64) with a SQL store, the default | Version: on the server host or inside its container run pip show mlflow, or mlflow --version. 3.3.0 to 3.9.x are exposed with no bypass needed, 3.10.0 to 3.14.x through the redirect and DNS bypass, 3.15.0 or later has the fix, and 3.16.0 or later is needed on IPv6 or NAT64 networks. Store: look at --backend-store-uri in the launch command (ps -ef \| grep 'mlflow server', or systemctl cat mlflow). No value means the default SQLite store, which qualifies. A file store only cannot hold webhooks (GitHub advisory notes). |
| the webhooks API is open (no --app-name basic-auth) and the host can reach internal targets | Open API: look at the launch command or service unit (ps -ef \| grep 'mlflow server', or systemctl cat mlflow). The auth plugin is enabled only when the command includes --app-name basic-auth (MLflow authentication documentation); without that flag the API is open, because the only webhook authorization is in that optional plugin. To confirm, send the server any REST request without credentials from another host: if it is served instead of rejected, the API is open. Network reach: read the bind address in the launch command (--host), run ss -ltnp \| grep -i mlflow, then check the firewall, security group or reverse proxy rules for that port from an untrusted network. Outbound reach: from the server host run curl -s -m 3 -o /dev/null -w '%{http_code}\n' http://169.254.169.254/. On AWS, check whether IMDSv2 is required: aws ec2 describe-instances --instance-ids INSTANCE_ID --query 'Reservations[].Instances[].MetadataOptions.HttpTokens' (value required means IMDSv2 only). Review egress rules for the host. |

## Affected and fixed versions

| Product line | Affected | First fixed | Notes |
| --- | --- | --- | --- |
| MLflow Tracking Server (pip package mlflow) | 3.3.0 up to but excluding 3.15.0 | 3.15.0 (released 31 Jul 2026) | Fix is pull request #24258 (connection-time check of the peer address). Webhooks exist from 3.3.0; the URL guard from 3.10.0 |
| Follow-up hardening | 3.15.0 to 3.15.x | 3.16.0 | Pull request #25568 closes four IPv6-transition bypasses (NAT64, IPv4-mapped CGNAT) |

MLflow 3.3.0 introduced model-registry webhooks (3.3.0 release notes). The URL guard that this CVE bypasses, pull request #20747 (validate webhook URL), was merged on 13 Feb 2026 and shipped in 3.10.0. Releases 3.3.0 to 3.9.x have webhooks but predate that guard, so they are affected without needing a bypass; 3.10.0 to 3.14.x carry the guard and are affected through the redirect and DNS-rebinding bypass. 3.15.0 checks the peer address at connection time.

## If the fix cannot go in yet

- Upgrade to MLflow 3.15.0 or later, and to 3.16.0 or later on IPv6 or NAT64 networks. This is the fix. The advisory lists no workaround.
- Exposure-reducing steps if you cannot upgrade yet. The advisory states that webhook authorization lives in the optional auth plugin, so restart the server with mlflow server --app-name basic-auth (admin password from MLFLOW_AUTH_ADMIN_PASSWORD) and keep it off untrusted networks. Cost: every client and script needs credentials, and users must sign in.
- Require IMDSv2 (or the equivalent metadata protection) on the host and filter its outbound traffic, since the advisory names cloud instance metadata as the main target. Cost: software on the host that still uses IMDSv1 breaks, and webhooks to legitimate destinations need explicit allow rules.
- CISA's KEV entry gives this required action: apply mitigations in accordance with vendor instructions, follow the BOD 26-04 guidance the entry cites, and discontinue use of the product if mitigations are unavailable.

## What to look for

- No indicators of compromise have been published for this CVE. Search web server or reverse proxy access logs for webhook calls, for example grep -E 'POST /api/2.0/mlflow/webhooks(/[^ /]+/test)? ' access.log; a test call with a 200 status that you did not make is the pattern to investigate. List the registered webhooks with the API call GET /api/2.0/mlflow/webhooks (for example curl -s 'http://MLFLOW_HOST:5000/api/2.0/mlflow/webhooks?max_results=100') and read the url of each entry: any webhook that points at a host you do not recognize is a candidate.
- Review egress and flow logs from the server host for connections to 169.254.169.254 or to private and loopback ranges that the server has no reason to contact.
- If the host has a cloud role, review cloud audit logs for use of its temporary credentials from addresses outside your environment (general step).

## Timeline

| Date | Event | Source |
| --- | --- | --- |
| 13 Feb 2026 | Pull request #20747 adds the webhook URL guard that this CVE later bypasses; it ships in MLflow 3.10.0. | [source](https://github.com/mlflow/mlflow/pull/20747) |
| 12 Jun 2026 | freeman-bb reports the flaw privately through the GitHub advisory process. | [source](https://api.github.com/advisories?cve_id=CVE-2026-64849) |
| 26 Jun 2026 | The same flaw is reported publicly in issue #24179 by an independent finder (the advisory credits the 12 Jun private report with discovery priority). | [source](https://github.com/mlflow/mlflow/issues/24179) |
| 2 Jul 2026 | The fix, pull request #24258, is merged. | [source](https://github.com/mlflow/mlflow/pull/24258) |
| 31 Jul 2026 | MLflow 3.15.0 is released with the fix. | [source](https://github.com/mlflow/mlflow/releases/tag/v3.15.0) |
| 17 Aug 2026 | GitHub publishes the advisory GHSA-7gwp-5pfp-969j and NVD publishes CVE-2026-64849 (CVSS 3.1 base score 9.3). | [source](https://api.github.com/advisories?cve_id=CVE-2026-64849) |
| 19 Aug 2026 | CISA adds the CVE to KEV with a due date of 2 Sep 2026. | [source](https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-64849) |
| 4 Sep 2026 | MLflow 3.16.0 is released with pull request #25568 (merged 3 Sep 2026), which closes four IPv6-transition bypasses of the 3.15.0 fix. | [source](https://github.com/mlflow/mlflow/pull/25568) |

The earliest dated mark of exploitation is CISA's, on 19 Aug 2026, 2 days after disclosure; exploitation may have begun earlier.

## Exploitation reported so far

The KEV entry cites the fix pull request and the public issue, and lists ransomware campaign use as Unknown. Neither it nor the NVD record names the attackers, the targets or the first day of use, so attacks may have begun before the KEV listing.

The CISA coordinator SSVC entry on the NVD record, stamped 20 Aug 2026, rates exploitation as active and the flaw as automatable. The entry is stamped one day after the KEV listing, so it adds no earlier date.

## Why runtime reachability settles it

A version below 3.15.0 is not enough: exposure needs the webhooks API open without authentication, a network path to the server and outbound reach to something worth stealing. Those are facts about the running server and its host, which the checks table reads one by one. KEV marks the CVE as exploited, so a reachable open server is urgent. See [runtime reachability](/methods/runtime-reachability/) for what the method proves and misses.

## Related pages

- [CVE-2026-42018: JFrog Artifactory](/ledger/cve-2026-42018/)
- [CVE-2026-19490: Citrix NetScaler ADC and Gateway](/ledger/cve-2026-19490/)
- [CVE-2026-65660: Microsoft SharePoint Server, SharePoint code injection](/ledger/cve-2026-65660/)

## Sources

- CVE-2026-64849: NVD record: https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-64849 (read 19 Nov 2026)
- CVE-2026-64849: CISA KEV entry (feed version 2026.11.18): https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-64849 (read 19 Nov 2026)
- CVE-2026-64849: vendor advisory (MLflow GitHub security advisory GHSA-7gwp-5pfp-969j, read through the GitHub advisory API record): https://github.com/mlflow/mlflow/security/advisories/GHSA-7gwp-5pfp-969j (read 19 Nov 2026)
- CVE-2026-64849: GitHub advisory API record (affected range, dates, credits): https://api.github.com/advisories?cve_id=CVE-2026-64849 (read 19 Nov 2026)
- CVE-2026-64849: vendor fix pull request: https://github.com/mlflow/mlflow/pull/24258 (read 19 Nov 2026)
- CVE-2026-64849: public issue report: https://github.com/mlflow/mlflow/issues/24179 (read 19 Nov 2026)
- CVE-2026-64849: vendor release notes for 3.15.0: https://github.com/mlflow/mlflow/releases/tag/v3.15.0 (read 19 Nov 2026)
- CVE-2026-64849: MLflow authentication documentation: https://mlflow.org/docs/latest/self-hosting/security/basic-http-auth/ (read 19 Nov 2026)
- CVE-2026-64849: vendor pull request that added the URL guard: https://github.com/mlflow/mlflow/pull/20747 (read 19 Nov 2026)
- CVE-2026-64849: vendor release notes for 3.3.0: https://github.com/mlflow/mlflow/releases/tag/v3.3.0 (read 19 Nov 2026)
- CVE-2026-64849: vendor follow-up pull request: https://github.com/mlflow/mlflow/pull/25568 (read 19 Nov 2026)

Last reviewed 19 Nov 2026. Canonical: https://reachabilityanalysis.com/ledger/cve-2026-64849/
