CVE-2026-10803 json
MLflow Dataset Digest Computation digest_utils.py mlflow.data.digest_utils weak hash
published 2026-06-04 5 mo ago modified 2026-09-08 2 mo ago also BIT-mlflow-2026-10803 , EUVD-2026-34245 , GHSA-5qmp-p3c4-72qj , PYSEC-2026-195
- cvss
- 3.6
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.1%
- EPSS 0.1% chance of exploitation in 30 days, percentile 0%
- public exploits
- 0
- none known
Summary
A flaw has been found in MLflow up to 3.10.0. This issue affects the function mlflow.data.digest_utils of the file mlflow/data/digest_utils.py of the component Dataset Digest Computation. This manipulation causes use of weak hash. It is possible to launch the attack on the local host. The attack is considered to have high complexity. The exploitability is assessed as difficult. The exploit has been published and may be used. The project was informed of the problem early through a pull request but has not reacted yet.
Patch / fix
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-10803 updated cvss 2.5
mlflow: MLflow: Use of weak hash in Dataset Digest Computation
-
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: 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
- 5 mo ago
Exploit prediction
0.10% chance of exploitation in the next 30 days, higher than 0% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/mlflow/mlflow/issues/22419 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 2.0 | CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/VI:L/VA:L/SC:N/SI:N/SA:N/E:P |
| CNA | 3.1 | 3.6 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L/E:P/RL:X/RC:R |
| CNA | 3.0 | 3.6 | CVSS:3.0/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L/E:P/RL:X/RC:R |
| CNA | 2.0 | 2.4 | AV:L/AC:H/Au:S/C:N/I:P/A:P/E:POC/RL:ND/RC:UR |
| GitHub | 3.1 | 3.6 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L |
| CNA | 4.0 | 1.1 | CVSS:4.0/AV:L/AC:H/AT:N/PR:L/UI:N/VC:N/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 | 3.6 | CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L |
| CNA | 2.0 | 2.4 | AV:L/AC:H/Au:S/C:N/I:P/A:P |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| pypi | mlflow | <3.10.1 |
3.10.1 |
| bitnami | mlflow | <3.10.1 |
3.10.1 |
Affected products
- n/a MLflow
Classification
References
-
github.com
/mlflow/mlflow/pull/22420
issue-tracking, patch, web, report
-
github.com
/mlflow/mlflow/issues/22419
exploit, issue-tracking, web, mitigation, evidence, report
-
vuldb.com
/vuln/368252
vdb-entry, technical-description, web, third-party-advisory, advisory
-
vuldb.com
/vuln/368252/cti
signature, permissions-required, web, vdb-entry, report
-
vuldb.com
/cve/CVE-2026-10803
third-party-advisory, web, vdb-entry, advisory
-
vuldb.com
/submit/831462
third-party-advisory, web, vdb-entry, advisory
-
github.com
/mlflow/mlflow/
product, web
-
nvd.nist.gov
/vuln/detail/CVE-2026-10803
advisory, web
-
github.com
/mlflow/mlflow
package
-
github.com
/pypa/advisory-database/tree/main/vulns/mlflow/PYSEC-2026-195.yaml
web
-
github.com
/advisories/GHSA-5qmp-p3c4-72qj
advisory
Sources
- CVE List CVE-2026-10803
- GitHub Advisory GHSA-5qmp-p3c4-72qj
- NVD CVE-2026-10803
- OSV BIT-mlflow-2026-10803
- OSV PYSEC-2026-195
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.