CVE-2025-15381: In the latest version of mlflow/mlflow, when the `basic-auth` app is enabled, tracing and assessment endpoints

Routine

HIGH 7.1MITIGATE

CVE-2025-15381 is a high-severity flaw (CVSS 7.1) affecting mlflow. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 c

Why this priority

High severity
Public exploit reference

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	7.1 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 72%)
CISA exploited list	No
Weakness	CWE-200, CWE-425
Published	2026-03-27
Last modified	2026-10-12

Publisher (CNA): huntr.dev · Vendor: lfprojects

Last updated 2026-10-12 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-27 17:16 UTCPublished CVE record published
2026-10-12 22:10 UTCUpdated Record last modified

lfprojects mlflow MITIGATE

Affected: all versions

Fixed in: no fixed release known

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy mlflow || rpm -q mlflow || mlflow --version

No fixed or unaffected release known

Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-15381?

mlflow: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2025-15381 being exploited?

CVE-2025-15381 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-15381 affect?

CVE-2025-15381 affects mlflow. Severity is high (CVSS 7.1). 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 expe

How urgent is CVE-2025-15381?

Priority 37/100. High severity; Public exploit reference

Related CVEs

CVE-2026-64849 CRITICAL 9.3 EXPLOITED UPGRADE MLflow Server-Side Request Forgery Vulnerability
CVE-2026-8147 HIGH 8.1 UPGRADE In MLflow versions prior to 3.14.0, when running with authentication enabled, the trace API endpoints lack pro
CVE-2026-2611 CRITICAL 9.6 UPGRADE In MLflow version 3.9.0, the MLflow Assistant feature introduced improper origin validation in its /ajax-api e
CVE-2025-15379 CRITICAL 10.0 UPGRADE A command injection vulnerability exists in MLflow's model serving container initialization code, specifically
CVE-2026-2614 HIGH 7.5 UPGRADE A vulnerability in the `_create_model_version()` handler of `mlflow/server/handlers.py` in mlflow/mlflow versi

References

← Back to latest CVEs