Quick answers
- Is CVE-2026-31237 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-31237 being exploited in the wild.
- How severe is CVE-2026-31237?
- Critical severity, with a CVSS score of 9.8, published 12 May 2026.
- Which products and versions are affected?
- Ludwig AI Ludwig <= 0.10.4, thru 0.10.4; ludwig (PyPI) ECOSYSTEM:introduced=0,last_affected=0.10.4.
- Is there a fix for CVE-2026-31237?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-31237 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-31237?
- Check whether you run Ludwig AI Ludwig or ludwig (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
Ludwig (up to version 0.10.4) is vulnerable to insecure deserialization (CWE-502) within its predict() method. When a dataset file path is provided, the framework automatically identifies the file format; if a .pkl file is detected, it is processed using pandas.read_pickle() without validation. Because the underlying Python pickle module is inherently unsafe, an attacker can craft a malicious pickle file that executes arbitrary code upon deserialization. This can be triggered remotely if the application exposes the prediction interface to untrusted input, requiring no authentication or user interaction. As of the advisory date, no patched version has been identified.
Affected products
- ludwig-ai ludwig <= 0.10.4
Identifiers
- CVE-2026-31237
- GHSA-wcr3-gm9f-f87q
- PYSEC-2026-404
Timeline
- 2026-05-12: disclosed: CVE-2026-31237 published
- 2026-05-12: advisory: GHSA-wcr3-gm9f-f87q published