Skip to content
Noroxi
NVD / CVE Program· CNA GitHub_M

CVE-2026-64849: MLflow: Unauthenticated full-read SSRF in webhook delivery: _validate_webhook_url bypassed via unvalidated HTTP redirects (and DNS rebinding)

Noroxi assessment

Priority: This week (action score 70/100)

  • CISA has confirmed exploitation in the wild (Aug 19, 2026). Remediation deadline for US federal agencies: Sep 2, 2026.
  • A ready-made attack module is public (Nuclei); exploiting it takes no special expertise.
  • Probability of exploitation in the next 30 days: 10% (FIRST EPSS); higher than 95.6% of all records.
  • Anyone who can reach it over the internet can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
  • According to CISA the attack is automatable: targets can be found by mass scanning.
  • Fixed version: mlflow mlflow 3.15.0.

Don’t wait for the next maintenance window. Upgrade to mlflow mlflow 3.15.0 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · CISA KEV · FIRST EPSS

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.

CriticalCVSS 9.3 · v3.1KEVWeaponized Fix available
Published
Aug 17, 2026
Updated
Oct 26, 2026
EPSS
10.0% · 95th percentile

Report tools

JSON

Action score

70

This week

Don’t wait for the next maintenance window.

CVSS
37 / 40 · 9.3 / 10
CISA KEV
30 / 30 · Listed
EPSS
3 / 30 · 10.0%

CISA SSVC decision

Exploitation
active
Automatable
yes
Technical impact
partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD
—
CNA · GitHub_M
9.3
NVD has not scored this yet; the score shown is the CNA’s.

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Actively exploited in the wild

CISA added this to its Known Exploited Vulnerabilities catalog on Aug 19, 2026. That signals real attacks, not theory.

Remediation deadline for US federal agencies: Sep 2, 2026.

Get told when this record changes

  • In CISA KEV: exploitation in the wild confirmed
  • Weaponized exploit exists
  • A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Follow CVE-2026-64849

When you'll hear from us

  • when it enters CISA KEV
  • when exploit code appears or is weaponized
  • when the record is updated (including a fixed version)
  • when EPSS rises 20 points in a week

One daily email digest (06:00 UTC); connect a webhook for KEV listings and weaponized exploits instantly.

Your free account also gets you

Running WordPress? Scan your site free with WP Lens

  • Stack alerts: add the products and versions you run, get the new CVEs that affect them
  • Uptime monitoring: 1 site, instant email when it goes down
  • Add your domain: subdomains and takeover risk scanned every week (1 domain)
  • 10 scans an hour on the security tools (3 a day without an account), an API key and MCP
  • All your scans in one panel: findings, what changed in the last scan, a report per domain or per client (PDF, share link)
All free tools

Sign up with email · Have an account? Sign in

Free account, no card. Unfollow any time.

Don't want an account? Get "Exploited this week" by email every MondayDon't want an account? RSS feed for lfprojects records

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

VendorProduct
lfprojectsmlflow

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

  • lfprojects mlflow3.3.0 and later · before 3.15.0

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

  • mlflow mlflow

    • >= 3.3.0, < 3.15.0affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

EcosystemPackageAffected rangeFix
PyPImlflowfrom 3.3.0 · before 3.15.03.15.0
PyPImlflowbefore 3.15.03.15.0

Same product

lfprojects: all records

Other highest-scoring records for the same primary product.

  • CVE-2023-3765Absolute Path Traversal in mlflow/mlflow
    60This week
  • CVE-2023-1177Path Traversal: '\..\filename' in mlflow/mlflow
    60This week
  • CVE-2023-6909Path Traversal: '\..\filename' in mlflow/mlflow
    57Plan

Published before and after this one in the same product

  • ← EarlierCVE-2026-10803Jun 4, 2026 · MLflow Dataset Digest Computation digest_utils.py mlflow.data.digest_utils weak hash
    4Monitor
  • ← EarlierCVE-2026-13484Jun 28, 2026 · MLflow Experiment-scoped Label Schema CRUD API authorization
    5Monitor
  • ← EarlierCVE-2026-8147Jul 2, 2026 · Authorization Bypass in mlflow/mlflow
    32Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / packageFixed versionSource
mlflow mlflow3.15.0 · descriptionVendor (CNA)
PyPI:mlflow3.15.0Package registry (OSV)

Exploit status

Weaponized

A ready exploit tool or active in-the-wild use is known for this vulnerability. This should be your top priority.

Evidence

  • Nuclei detection template ×1
  • Proof-of-concept repository on GitHub ×5

Noroxi does not host or link to exploit code. Metasploit module names and Nuclei template ids are shown (names, not code); Exploit-DB entries and PoC repositories are given as counts only.

Public exploit evidence
SourceKindDate
Nuclei detection templateNuclei template CVE-2026-64849 —
Proof-of-concept repository on GitHubstars:02026-08-18
Proof-of-concept repository on GitHubstars:02026-08-19
Proof-of-concept repository on GitHubstars:02026-08-19
Proof-of-concept repository on GitHubstars:02026-09-06
Proof-of-concept repository on GitHubstars:02026-10-25

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

  1. Published
  2. First PoCsame day
  3. CISA KEV+1 d
  4. TodayNov 4, 2026+79 d
EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

  • CVE-2026-239398 days apartServer-Side Request Forgery (SSRF) in mlflow/mlflow
    28Monitor
  • CVE-2025-52967420 days apartgateway_proxy_handler in MLflow before 3.1.0 lacks gateway_path validation.
    23Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

  • Anyone who can reach it over the internet can trigger it.
  • No account or password is required.
  • No user action is required.
  • No special conditions are required; it is repeatable.

If successful

Confidentiality
high · data can be read
Integrity
low · data or configuration can be modified
Availability
none

Impact can extend beyond the vulnerable component (scope changes).

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality impact
High
Integrity impact
Low
Availability impact
None

Weakness class (CWE)

CWE-918 · Server-Side Request Forgery (SSRF)

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N

nvd-secondary

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

ATT&CK techniques

—

Change log

  1. Fix✗ → ✓

For records you follow, these changes also arrive as notifications. →

References

Show all references (3 more)

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records