What is CVE-2026-69148?
MLflow is an open source AI engineering platform for agents, large language models, and machine learning models. Prior to 3.15.0, CreateModelVersion accepts a run_id or model_id after _validate_source_run() or _validate_source_model() in mlflow/server/handlers.py verifies only path containment, allowing authenticated users to create a model version that references another user's artifact directory and read files through GET /model-versions/get-artifact without the required READ permission. This issue is fixed in version 3.15.0.
The record classifies CVE-2026-69148 under weakness class CWE-862. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs low-privilege credentials, needs no user interaction, and has high impact on confidentiality. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 49 days ago.
Severity and exploitation probability
- CVSS v3.1 base score
- 7.1 — HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:L/A:N - EPSS (FIRST)
- 0.2% probability of exploitation in the next 30 days, higher than 12.3% of all scored CVEs
- CISA KEV
- Not listed in the CISA Known Exploited Vulnerabilities catalog
- Threadlinqs priority
- 4/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
- Published
- 2026-08-17, last modified 2026-08-18
Is CVE-2026-69148 being exploited?
It currently carries a trending score of 33 in the Threadlinqs vulnerability feed.
Affected products and versions
- mlflow: mlflow
Affected software packages:
npm:mlflow— patched in 3.15.0
How to fix CVE-2026-69148
Fixed versions are recorded for 1 package: npm:mlflow 3.15.0. No vendor patch reference has been recorded for CVE-2026-69148 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.
Threat activity tracking CVE-2026-69148
No threat campaign in the Threadlinqs corpus currently references CVE-2026-69148, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.
Sources
Enriched from CVE.org, FIRST EPSS, GitHub Security Advisories. Last verified by Threadlinqs on .