# CVE-2026-31237: Ludwig framework is vulnerable to insecure deserialization through its predict() method.

> A remote attacker can execute arbitrary code by providing a malicious pickle file to the predict method in the Ludwig framework.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 14 May 2026
- **Also known as:** GHSA-wcr3-gm9f-f87q, PYSEC-2026-404

## What is CVE-2026-31237?

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.

### Official 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.

Weakness: CWE-502 (Deserialization of Untrusted Data)

## Which versions are affected by CVE-2026-31237?

3 open source packages ship an affected version, including ludwig.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ludwig` | PyPI | All versions to 0.10.4 | None |
| `ludwig` | PyPI | All versions to 0.10.4 | None |
| `ludwig` | PyPI | All versions to 0.10.4 | None |

## How do I fix CVE-2026-31237?

No fix has been published for CVE-2026-31237 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-31237 being exploited?

There is no known exploitation of CVE-2026-31237 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-31237 and fix it if it is affected.

What 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.
Exploitation: There is no known exploitation of CVE-2026-31237 in the wild and no public exploit code.

Affected packages and fixed versions:
- ludwig (PyPI): affected all versions up to 0.10.4; no fix listed
- ludwig (PyPI): affected all versions up to 0.10.4; no fix listed
- ludwig (PyPI): affected all versions up to 0.10.4; no fix listed

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-31237/ (Markdown: https://insights.sbomify.com/CVE-2026-31237/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-31237
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-31237
- OSV: https://osv.dev/vulnerability/CVE-2026-31237

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-31237/
Summaries are generated and may contain mistakes; the official description above is the record.