# CVE-2026-10766: mlrun DataFrame Hash helpers.py mlrun.utils.helpers.calculate_dataframe_hash weak hash

> A weak hash implementation in mlrun allows local attackers to potentially bypass integrity checks, requiring high complexity and local access.

- **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:** No
- **Published:** 3 Jun 2026
- **Updated:** 4 Jun 2026
- **Also known as:** GHSA-phx2-3w66-h4pw, PYSEC-2026-3487

## What is CVE-2026-10766?

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

### Official description

A vulnerability has been found in mlrun up to 1.12.0-rc3. This impacts the function mlrun.utils.helpers.calculate_dataframe_hash of the file mlrun/utils/helpers.py of the component DataFrame Hash Handler. The manipulation leads to use of weak hash. The attack can only be performed from a local environment. The complexity of an attack is rather high. The exploitability is said to be difficult. The exploit has been disclosed to the public and may be used. The pull request to fix this issue awaits acceptance.

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

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

3 open source packages ship an affected version, including mlrun.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mlrun` | PyPI | All versions to 1.12.0rc3 | None |
| `mlrun` | PyPI | All versions to 1.12.0rc3 | None |
| `mlrun` | PyPI | All versions to 1.12.0rc3 | None |

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

No fix has been published for CVE-2026-10766 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-10766 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10766 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-10766 and fix it if it is affected.

What it is: CVE-2026-10766 is a low-severity vulnerability in mlrun, published on 3 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-10766 exists.

Affected packages and fixed versions:
- mlrun (PyPI): affected all versions up to 1.12.0rc3; no fix listed
- mlrun (PyPI): affected all versions up to 1.12.0rc3; no fix listed
- mlrun (PyPI): affected all versions up to 1.12.0rc3; no fix listed

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

## Sources

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

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