{"answers":{"affected":"3 open source packages ship an affected version, including ludwig.","exploited":"There is no known exploitation of CVE-2026-31237 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-31237 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-31237 is a critical unsafe deserialization vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-31237 and fix it if it is affected.\n\nWhat it is: CVE-2026-31237 is a critical unsafe deserialization vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-31237 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- ludwig (PyPI): affected all versions up to 0.10.4; no fix listed\n- ludwig (PyPI): affected all versions up to 0.10.4; no fix listed\n- ludwig (PyPI): affected all versions up to 0.10.4; 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-31237/ (Markdown: https://insights.sbomify.com/CVE-2026-31237/index.md)","id":"CVE-2026-31237","markdown":"https://insights.sbomify.com/CVE-2026-31237/index.md","name":"CVE-2026-31237","record":{"aliases":["GHSA-wcr3-gm9f-f87q","PYSEC-2026-404"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Python ML library","requires_auth":"none","summary":"A remote attacker can execute arbitrary code by providing a malicious pickle file to the predict method in the Ludwig framework.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"The Ludwig framework thru 0.10.4 is vulnerable to insecure deserialization (CWE-502) through its predict() method. When a user provides a dataset file path to the predict() method, the framework automatically determines the file format. If the file is a pickle (.pkl) file, it is loaded using pandas.read_pickle() without any validation or security restrictions. This allows the deserialization of arbitrary Python objects via the unsafe pickle module. A remote attacker can exploit this by providing a maliciously crafted pickle file, leading to arbitrary code execution on the system running the Ludwig prediction.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Ludwig framework is vulnerable to insecure deserialization through its predict() method.","id":"CVE-2026-31237","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":3,"n_references":2,"next":{"headline":"Ludwig framework is vulnerable to insecure deserialization in its model serving component","id":"CVE-2026-31238"},"packages":[{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.10.4"],"package":"ludwig","purl":null,"source":"GHSA-wcr3-gm9f-f87q"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.10.4"],"package":"ludwig","purl":"pkg:pypi/ludwig","source":"GHSA-wcr3-gm9f-f87q"},{"ecosystem":"PyPI","fixed":[],"introduced":["0"],"last_affected":["0.10.4"],"package":"ludwig","purl":"pkg:pypi/ludwig","source":"PYSEC-2026-404"}],"prev":{"headline":"llm CLI tool contains a code injection vulnerability via `--functions` command-line argument","id":"CVE-2026-31236"},"products":["n/a"],"published":"2026-05-12","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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-14","vendors":["n/a"]},"summary":"A remote attacker can execute arbitrary code by providing a malicious pickle file to the predict method in the Ludwig framework.","url":"https://insights.sbomify.com/CVE-2026-31237/"}