Code execution via unvalidated pickle deserialization
Published May 12, 2026 · Updated May 12, 2026
Insecure deserialization in Snorkel 0.10.0 and earlier allows remote attackers to execute arbitrary code via a crafted label-model file. BaseLabeler.load() opens the caller-supplied source path and passes its contents directly to pickle.load(), which reconstructs attacker-controlled objects without validation. Execution occurs only when an application or user loads the malicious file, and the payload runs with the privileges of the hosting Python process.
Summary
What happened
Insecure deserialization in Snorkel 0.10.0 and earlier allows remote attackers to execute arbitrary code via a crafted label-model file. BaseLabeler.load() opens the caller-supplied source path and passes its contents directly to pickle.load(), which reconstructs attacker-controlled objects without validation. Execution occurs only when an application or user loads the malicious file, and the payload runs with the privileges of the hosting Python process.
The record
- CVE
- CVE-2026-31223
- Published
- May 12, 2026
- Updated
- May 12, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-502, T1204.002
- 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.
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.
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