Remote code execution via unsafe pickle dataset loading
Published May 12, 2026 · Updated May 12, 2026
Insecure deserialization in Ludwig 0.10.4 and earlier allows remote attackers to execute arbitrary code through a crafted pickle dataset. The predict() path identifies .pkl input and passes the attacker-controlled file to pandas.read_pickle() without validation or deserialization restrictions. The attacker must be able to make a Ludwig prediction consume the crafted dataset; code runs with the prediction process's privileges.
Summary
What happened
Insecure deserialization in Ludwig 0.10.4 and earlier allows remote attackers to execute arbitrary code through a crafted pickle dataset. The predict() path identifies .pkl input and passes the attacker-controlled file to pandas.read_pickle() without validation or deserialization restrictions. The attacker must be able to make a Ludwig prediction consume the crafted dataset; code runs with the prediction process's privileges.
The record
- CVE
- CVE-2026-31237
- Published
- May 12, 2026
- Updated
- May 12, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-502, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 12, 2026CVE publishedPublication date reported by the CVE source.
- May 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo