CYBERSECURITYTRACKER
TRACKING
Vulnerabilities

CVE-2026-64849

Review this vulnerability's source-backed evidence, with unavailable values and read failures kept distinct.

A permanent, source-backed tracker page. Values are shown only when returned; explicit gaps and read failures remain different states.

Full record read. Reported values and explicit gaps below come from the tracked record.

Detection and validation

Mapped metadata availability only. These signals do not change priority.

  • Sigma

    Not mapped by tracked sources.

  • Atomic

    Not mapped by tracked sources.

  • Nuclei

    MLflow Webhook SSRF - Unauthenticated Full-Read via Redirect Bypass. Check identifier: CVE-2026-64849.

    Open Nuclei metadata

  • Metasploit

    Not mapped by tracked sources.

What it is

Reported

MLflow contains a server-side request forgery vulnerability that can allow attackers to reach internal or cloud metadata services and receive response_status and response_body.

Source reported · Source: NVD · Source last published: · Source description excerpt; complete tracked detail loads below. · Source last updated:

What is affected

Reported

MLflow; MLflow. Product-level identification only; no affected-version conclusion is available from this field.

Source reported · Source: NVD · Source last published: · Source last updated:

Urgency and basis

Reported

Act · 462.2

Tracker computed · Tracker decision tier from the evidence detailed below · Source last updated:

Exploitation evidence

Reported

Active exploitation · CISA KEV · VulnCheck KEV · ENISA exploited-vulnerability catalog

Source reported · Active since: · CISA KEV added: · VulnCheck KEV added: · ENISA added: · Source last updated:

What to do

Reported

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.

Source remediation ↗

Source reported · Tracked source remediation field · Source last updated:

Evidence detail

Loading the full tracker evidence record…

Glossary

Open in glossary