CVE-2025-15381 | Unauthorized Access to Tracing and Assessment Endpoints in mlflow/mlflow

In the latest version of mlflow/mlflow, when the `basic-auth` app is enabled, tracing and assessment endpoints are not protected by permission validators. This allows any authenticated user, including those with `NO_PERMISSIONS` on the experiment, to read trace information and create assessments for traces they should not have access to. This vulnerability impacts confidentiality by exposing trace metadata and integrity by allowing unauthorized creation of assessments. Deployments using `mlflow server --app-name=basic-auth` are affected.

Published: 2026-03-27 Last update: 2026-03-30 Assigner: [email protected] Source: [email protected]
NVD Status：Undergoing Analysis，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-15381 is rated Moderate Risk (40.9/100): CVSS High severity, with low exploitation likelihood (EPSS 0.32%). Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-15381

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.01% 0.32% +0.31%
2 2026-03-28 — 0.01% —

Full EPSS history (2 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-15381

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.1 3.0 HIGH
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
 2.8 5.2 [email protected]

Weakness enumeration for CVE-2025-15381

GitHub Security Advisory for CVE-2025-15381

GHSA-g6pg-52vf-843h · Severity: high · Ecosystem: pip — MLFlow allows Tracing + Assessments Access

OS Trackers for CVE-2025-15381

vendor priority summary link
redhat high — https://access.redhat.com/security/cve/CVE-2025-15381

Affected software / configurations for CVE-2025-15381

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-15381

cvelogic Threat Intelligence