# CVE-2026-13484: MLflow Experiment-scoped Label Schema CRUD API authorization

> Attackers can bypass authorization checks in the MLflow Experiment-scoped Label Schema CRUD API to read or modify data.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **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:** 28 Jun 2026
- **Updated:** 30 Jun 2026
- **Also known as:** BIT-mlflow-2026-13484, GHSA-wfp4-8wh2-c48v, MINI-rmfj-w9wj-cp4j

## What is CVE-2026-13484?

CVE-2026-13484 is a low-severity missing authorization vulnerability in Lfprojects Mlflow, published on 28 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in MLflow up to 4666cffc7912ea606d592fc38d6a75e2935f65e7. The impacted element is an unknown function of the component Experiment-scoped Label Schema CRUD API. Such manipulation leads to missing authorization. It is possible to launch the attack remotely. A high complexity level is associated with this attack. The exploitability is regarded as difficult. The exploit has been disclosed to the public and may be used. A reply to the GitHub issue explains, that "[t]he labeling schema PR has not been merged yet. The auth handlers will be added before the release."

Weakness: CWE-863 (Incorrect Authorization), CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-13484?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mlflow` | Bitnami | All versions | 3.13.0 |

Products: Lfprojects Mlflow.

## How do I fix CVE-2026-13484?

Upgrade mlflow to 3.13.0 or later.

## Is CVE-2026-13484 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13484 exists.

## 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-2026-13484 and fix it if it is affected.

What it is: CVE-2026-13484 is a low-severity missing authorization vulnerability in Lfprojects Mlflow, published on 28 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-13484 exists.

Affected packages and fixed versions:
- mlflow (Bitnami): affected all versions; fixed in 3.13.0

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-2026-13484/ (Markdown: https://insights.sbomify.com/CVE-2026-13484/index.md)
```

## Sources

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

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