What is CVE-2026-10766?

CVE-2026-10766 is a low-severity use of a broken or risky cryptographic algorithm vulnerability in mlrun (pip), affecting versions <= 1.12.0rc3. No fixed version is listed yet. The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES.

How severe is CVE-2026-10766?

CVE-2026-10766 has a CVSS score of 3.6 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Which versions of mlrun are affected by CVE-2026-10766?

mlrun (pip) versions <= 1.12.0rc3 is affected.

Is there a fix for CVE-2026-10766?

No fixed version is listed for CVE-2026-10766 yet. Monitor the advisory for updates and apply mitigations in the interim.

Is CVE-2026-10766 exploitable, and should I be worried?

Whether CVE-2026-10766 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2026-10766 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2026-10766 in mlrun

Q: How severe is CVE-2026-10766?

CVE-2026-10766 has a CVSS score of 3.6 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.

Q: Which versions of mlrun are affected by CVE-2026-10766?

mlrun (pip) versions <= 1.12.0rc3 is affected.

Q: Is there a fix for CVE-2026-10766?

No fixed version is listed for CVE-2026-10766 yet. Monitor the advisory for updates and apply mitigations in the interim.

Q: Is CVE-2026-10766 exploitable, and should I be worried?

Whether CVE-2026-10766 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

Q: What actually determines whether CVE-2026-10766 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

Q: How do I fix CVE-2026-10766?

No fixed version is listed yet. In the interim: Replace the broken algorithm with a current recommendation: SHA-256 or higher for hashing, AES-GCM for symmetric encryption.

Summary

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

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.

Impact

The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES. Typical impact: compromised confidentiality or integrity of protected data.

CVE-2026-10766 has a CVSS score of 3.6 (Low). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. No fixed version is listed yet, so configuration controls and monitoring matter more in the interim.

Affected versions

mlrun (<= 1.12.0rc3)

Security releases

Not available

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

No fixed version is listed for CVE-2026-10766 yet.

In the interim: Replace the broken algorithm with a current recommendation: SHA-256 or higher for hashing, AES-GCM for symmetric encryption.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2026-10766? CVE-2026-10766 is a low-severity use of a broken or risky cryptographic algorithm vulnerability in mlrun (pip), affecting versions <= 1.12.0rc3. No fixed version is listed yet. The application uses a cryptographic algorithm known to have weaknesses, such as MD5, SHA-1, or DES.
How severe is CVE-2026-10766? CVE-2026-10766 has a CVSS score of 3.6 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
Which versions of mlrun are affected by CVE-2026-10766? mlrun (pip) versions <= 1.12.0rc3 is affected.
Is there a fix for CVE-2026-10766? No fixed version is listed for CVE-2026-10766 yet. Monitor the advisory for updates and apply mitigations in the interim.
Is CVE-2026-10766 exploitable, and should I be worried? Whether CVE-2026-10766 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2026-10766 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2026-10766? No fixed version is listed yet. In the interim: Replace the broken algorithm with a current recommendation: SHA-256 or higher for hashing, AES-GCM for symmetric encryption.