LUDWIG · CVE-2026-31237 · Package
NO FIX YET · SEE WHAT TO DO
Ludwig, a Python machine learning framework, loads a dataset passed to its predict() method with pandas.read_pickle() when the file ends in .pkl, with no validation. An attacker who supplies a malicious pickle file can run arbitrary Python code on the machine running the prediction.
first public May 12, 2026 · 2 sources
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Teams that run Ludwig's predict() on dataset files they do not fully trust, such as user uploads or files fetched from external sources, are exposed. Pipelines that only predict on datasets their own team produced and controls are lower risk. unknown whether the sources list other conditions.
Not affected if no-predict-on-external-files, trusted-input-only
Who cares ludwig, machine-learning, python
pip show ludwig and treat anything at or below 0.10.4 as affected.predict() that take a dataset path or file that could come from outside your control.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.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.