CVE-2026-13484 json
MLflow Experiment-scoped Label Schema CRUD API authorization
published 2026-06-28 4 mo ago modified 2026-09-10 59 d ago also BIT-mlflow-2026-13484 , EUVD-2026-39984
- cvss
- 5.0
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 43%
- public exploits
- 0
- none known
Summary
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."
Patch / fix
- bitnami mlflow 3.13.0
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2026-13484 updated cvss 5.0
mlflow: MLflow: Unauthorized access and data manipulation via missing API authorization
-
Red Hat OpenShift AI (RHOAI) rhoai/odh-mlflow-rhel9, rhoai/odh-th06-cpu-torch210-py312-rhel9, rhoai/odh-th06-rocm64-torch291-py312-rhel9, rhoai/odh-th06-cuda130-torch210-py312-rhel9, rhoai/odh-training-cuda128-torch29-py312-rhel9, rhoai/odh-pipeline-runtime-pytorch-cuda-py312-rhel9, +13 moreaffected: workaround, no fix available “Fix deferred”
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 4 mo ago
Exploit prediction
0.50% chance of exploitation in the next 30 days, higher than 43% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/mlflow/mlflow/issues/23608 referenced PoC, tagged "exploit" by a source, unverified
- github.com https://github.com/mlflow/mlflow/issues/23608#issuecomment-4560963877 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 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 |
| CNA | 3.1 | 5.0 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:C |
| CNA | 3.0 | 5.0 | CVSS:3.0/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:C |
| CNA | 2.0 | 4.6 | AV:N/AC:H/Au:S/C:P/I:P/A:P/E:POC/RL:ND/RC:C |
| CNA | 4.0 | 1.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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| CNA | 3.1 | 5.0 | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:L |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| CNA | 2.0 | 4.6 | AV:N/AC:H/Au:S/C:P/I:P/A:P |
| OSV | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | mlflow | <3.13.0 |
3.13.0 |
Affected products
- n/a MLflow
Classification
References
-
github.com
/mlflow/mlflow/issues/23608
exploit, issue-tracking, third-party-advisory, advisory
-
github.com
/mlflow/mlflow/issues/23608#issuecomment-4560963877
issue-tracking, exploit, third-party-advisory, vdb-entry, advisory
-
vuldb.com
/vuln/374481
vdb-entry, third-party-advisory, advisory
-
vuldb.com
/vuln/374481/cti
signature, permissions-required, vdb-entry, report
-
vuldb.com
/cve/CVE-2026-13484
third-party-advisory, vdb-entry, advisory
-
vuldb.com
/submit/837658
third-party-advisory, vdb-entry, advisory
-
github.com
/mlflow/mlflow/
product, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-13484
web
Sources
- CVE List CVE-2026-13484
- NVD CVE-2026-13484
- OSV BIT-mlflow-2026-13484
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.