{"answers":{"affected":"3 open source packages ship an affected version, including mlrun.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10766 exists.","fix":"No fix has been published for CVE-2026-10766 yet. Limit exposure of the affected software until one is available.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-10766 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-10766 exists.\n\nAffected packages and fixed versions:\n- mlrun (PyPI): affected all versions up to 1.12.0rc3; no fix listed\n- mlrun (PyPI): affected all versions up to 1.12.0rc3; no fix listed\n- mlrun (PyPI): affected all versions up to 1.12.0rc3; no fix listed\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-10766/ (Markdown: https://insights.sbomify.com/CVE-2026-10766/index.md)","id":"CVE-2026-10766","markdown":"https://insights.sbomify.com/CVE-2026-10766/index.md","name":"CVE-2026-10766","record":{"aliases":["GHSA-phx2-3w66-h4pw","PYSEC-2026-3487"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"MLOps library","requires_auth":"low_privilege","summary":"A weak hash implementation in mlrun allows local attackers to potentially bypass integrity checks, requiring high complexity and local access.","user_interaction":"not_required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[],"cvss":{"score":2,"severity":"low","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-328","name":"Use of Weak Hash"},{"id":"CWE-327","name":"Use of a Broken or Risky Cryptographic Algorithm"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"mlrun DataFrame Hash helpers.py mlrun.utils.helpers.calculate_dataframe_hash weak hash","id":"CVE-2026-10766","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"weak_cryptography","year":"2026"},"n_packages":3,"n_references":7,"next":{"headline":"LocalGov Workflows - Moderately critical - Information disclosure - SA-CONTRIB-2026-039","id":"CVE-2026-10768"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.12.0rc3"],"package":"mlrun","purl":null,"source":"GHSA-phx2-3w66-h4pw"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.12.0rc3"],"package":"mlrun","purl":"pkg:pypi/mlrun","source":"GHSA-phx2-3w66-h4pw"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["1.12.0rc3"],"package":"mlrun","purl":"pkg:pypi/mlrun","source":"PYSEC-2026-3487"}],"prev":{"headline":"Information disclosure in BVMS 4.5 up to 12.3","id":"CVE-2026-10764"},"products":["mlrun"],"published":"2026-06-03","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-06-04","vendors":["n/a"]},"summary":"A weak hash implementation in mlrun allows local attackers to potentially bypass integrity checks, requiring high complexity and local access.","url":"https://insights.sbomify.com/CVE-2026-10766/"}