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

> Authenticated users can bypass permission checks to read trace data and create assessments in MLflow when basic-auth is enabled.

- **Severity:** High 8.1 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 27 Mar 2026
- **Updated:** 15 Jul 2026
- **Also known as:** CLSA-2026-1790340259, GHSA-g6pg-52vf-843h, PYSEC-2026-2657

## What is CVE-2025-15381?

CVE-2025-15381 is a high-severity missing authorization vulnerability in Lfprojects Mlflow, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-425 (Direct Request), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-15381?

3 open source packages ship an affected version, including mlflow. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mlflow` | PyPI | All versions to 3.8.1 | None |
| `mlflow` | PyPI | All versions to 3.8.1 | None |
| `mlflow` | PyPI | All versions to 3.8.1 | None |

Products: Lfprojects Mlflow.

## How do I fix CVE-2025-15381?

Apply the vendor's patch.

## Is CVE-2025-15381 being exploited?

There is no known exploitation of CVE-2025-15381 in the wild and no public exploit code.

## Other vulnerabilities in Lfprojects Mlflow

- [CVE-2026-64849](https://insights.sbomify.com/CVE-2026-64849/): MLflow Server-Side Request Forgery (critical 9.3, exploited in the wild)
- [CVE-2025-15379](https://insights.sbomify.com/CVE-2025-15379/): Command Injection in mlflow/mlflow (critical 10.0)
- [CVE-2024-0520](https://insights.sbomify.com/CVE-2024-0520/): Remote Code Execution due to Full Controlled File Write in mlflow/mlflow (critical 10.0)
- [CVE-2023-6977](https://insights.sbomify.com/CVE-2023-6977/): Path Traversal: '\..\filename' (critical 10.0)
- [CVE-2023-6709](https://insights.sbomify.com/CVE-2023-6709/): Improper Neutralization of Special Elements Used in a Template Engine in mlflow/mlflow (critical 10.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-15381 and fix it if it is affected.

What it is: CVE-2025-15381 is a high-severity missing authorization vulnerability in Lfprojects Mlflow, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-15381 in the wild and no public exploit code.

Affected packages and fixed versions:
- mlflow (PyPI): affected all versions up to 3.8.1; no fix listed
- mlflow (PyPI): affected all versions up to 3.8.1; no fix listed
- mlflow (PyPI): affected all versions up to 3.8.1; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-15381/ (Markdown: https://insights.sbomify.com/CVE-2025-15381/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-15381
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-15381
- OSV: https://osv.dev/vulnerability/CVE-2025-15381

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-15381/
Summaries are generated and may contain mistakes; the official description above is the record.