# CVE-2026-10803: MLflow Dataset Digest Computation digest_utils.py mlflow.data.digest_utils weak hash

> An attacker with local access can exploit weak hashing in MLflow dataset digests to potentially bypass integrity checks.


- **Severity:** Low 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 4 Jun 2026
- **Updated:** 4 Jun 2026
- **Also known as:** BIT-mlflow-2026-10803, GHSA-5qmp-p3c4-72qj, PYSEC-2026-195

## What is CVE-2026-10803?

CVE-2026-10803 is a low-severity vulnerability in Lfprojects Mlflow, published on 4 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

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.

Weakness: CWE-328 (Use of Weak Hash), CWE-327 (Use of a Broken or Risky Cryptographic Algorithm)

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

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


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

Products: Lfprojects Mlflow.

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

Upgrade mlflow to 3.10.1 or later.

## Is CVE-2026-10803 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10803 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-10803 and fix it if it is affected.

What it is: CVE-2026-10803 is a low-severity vulnerability in Lfprojects Mlflow, published on 4 Jun 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10803 exists.

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

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

## Sources

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

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