CVE Intelligence
Low Cryptography exploit reference

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

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.

Published Jun 4, 2026 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulDB

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.1% (30-day exploitation probability)+0
  • CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.1%
ahead of 1% of scored CVEs · Oct 15, 2026
Affects
Lfprojects
Mlflow
CVSS base
3.6
Low · 2 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Proof of concept
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented mitigation — github.com (NIST National Vulnerability Database)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Lfprojects Mlflow).
  2. Apply the documented mitigations until a definitive fix is available.
  3. Search available logs for exploit probes matching the vulnerability class (cryptography), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Lfprojects Mlflow ≤ 3.10.0 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
2.0 CVSS 4.0 Low — — VulDB via CVE Program (cve.org) e CISA ADP
1.1 CVSS 4.0 Low — — cna@vuldb.com via NIST National Vulnerability Database
3.6 CVSS 3.1 Low 1.0 2.5 cna@vuldb.com via NIST National Vulnerability Database
3.6 CVSS 3.1 Low — — VulDB via CVE Program (cve.org) e CISA ADP
3.6 CVSS 3.0 Low — — VulDB via CVE Program (cve.org) e CISA ADP
2.4 CVSS 2.0 Low 1.5 4.9 cna@vuldb.com via NIST National Vulnerability Database
2.4 CVSS 2.0 Low — — VulDB via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:L (score shown at the top: cna@vuldb.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-327 · Use of a Broken or Risky Cryptographic Algorithm

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 15, 2026 · 3 reading(s) · max 0.10%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Check TLS negotiations and unexpected certificates in the component’s traffic.
endpoint telemetry (EDR)network IDS/IPS

Timeline

What happened to this CVE, newest first.

  • 2026
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 3.6
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVE published
    Jun 4, 2026 · VulDB

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

7 on the record

Elsewhere on this site

Lfprojects
every CVE for this vendor
Cryptography
same class
CWE-327
other pages naming this weakness

Related CVEs (same products)

  • Critical CVE-2026-64849 MLflow Server-Side Request Forgery Vulnerability KEV Aug 17, 2026
  • High CVE-2026-8147 Authorization Bypass in mlflow/mlflow Jul 2, 2026
  • High CVE-2026-13484 MLflow Experiment-scoped Label Schema CRUD API authorization Jun 28, 2026
  • High CVE-2026-4035 Environment Variable Resolution Vulnerability in mlflow/mlflow Jun 3, 2026
  • Medium CVE-2026-3198 Improper Access Control in mlflow/mlflow Jun 2, 2026
  • Critical CVE-2026-2651 Missing Authorization Validation in mlflow/mlflow May 25, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2026-10803 is "MLflow Dataset Digest Computation digest_utils.py mlflow.data.digest_utils weak hash", rated Low. It affects Mlflow (Lfprojects); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 3.6 describes technical severity. EPSS 0.10% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.