Advisory record · GHSA-phx2-3w66-h4pw

mlrun: DataFrame hash collisions can cause dataset artifact path conflicts and silent data corruption

CVSS 2.0 LowEPSS 0.0008 · 1st percentile

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

PackageEcosystemAffectedFixed in
mlrunPyPI<=1.12.0rc3No fixed version yet
Identifiers
GHSA-phx2-3w66-h4pw · CVE-2026-10766 · PYSEC-2026-3487
Weakness (CWE)
CWE-327 · CWE-328
Published
3 Jun 2026
Updated
23 Jul 2026

Machine-written summary

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

mlrun versions up to and including 1.12.0rc3 are affected. The DataFrame hashing function in mlrun.utils.helpers uses a weak hash, so differing DataFrames can produce colliding hashes and dataset artifact paths. An attacker needs local access and the source describes exploitation as difficult; the result is possible silent data corruption. No fixed version is listed.

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

ScoreRatingCVSSVectorSource
2.0 Low 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 CNA (VulDB)
  • CISA KEV Not listed.
  • EPSS 0.0008, the 1st percentile, on 11 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:41 UTC First seen by agentprime
  2. 31 Oct 2026, 14:41 UTC Confirmed by OSV

Sources

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.