# 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 mani...

Advisory record · `GHSA-5qmp-p3c4-72qj`

- **Identifiers:** `GHSA-5qmp-p3c4-72qj` · `BIT-mlflow-2026-10803` · `CVE-2026-10803` · `PYSEC-2026-195`
- **State:** Confirmed
- **Severity:** CVSS 2.0 Low
- **Critical:** No
- **Weakness (CWE):** [CWE-327](https://cwe.mitre.org/data/definitions/327.html) · [CWE-328](https://cwe.mitre.org/data/definitions/328.html)
- **Tags:** [Weak cryptography or TLS](https://agentprime.io/advisories/tag/weak-crypto.md)
- **Published:** 4 Jun 2026
- **Updated:** 23 Jul 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 4 Jun 2026, 12:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `mlflow` (PyPI): affected `<3.10.1`; fixed in `3.10.1`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> MLflow versions before 3.10.1 are affected by a weak hash issue in the dataset digest computation in mlflow.data.digest_utils. An attacker with local access could exploit it, though the source describes the attack as highly complex and difficult to exploit, and a published exploit exists. Upgrade to MLflow 3.10.1 or later, which contains the fix.

Written 5 Nov 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 2.0 Low, CVSS 4.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`, from CNA (VulDB)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0010, the 1st percentile, on 12 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 14:42 UTC: First seen by agentprime
- 31 Oct 2026, 14:42 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/PYSEC-2026-195)

## Sources

- [GitHub Advisory Database: GHSA-5qmp-p3c4-72qj](https://github.com/advisories/GHSA-5qmp-p3c4-72qj)
- [OSV: GHSA-5qmp-p3c4-72qj](https://osv.dev/vulnerability/GHSA-5qmp-p3c4-72qj)
- <https://github.com/mlflow/mlflow/>
- <https://vuldb.com/cve/CVE-2026-10803>
- <https://vuldb.com/submit/831462>
- <https://vuldb.com/vuln/368252>
- <https://github.com/advisories/GHSA-5qmp-p3c4-72qj>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-5qmp-p3c4-72qj>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-5qmp-p3c4-72qj/>. Everything for agents: <https://agentprime.io/llms.txt>.