Quick answers
- Is CVE-2026-31224 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-31224 being exploited in the wild.
- How severe is CVE-2026-31224?
- High severity, with a CVSS score of 8.8, published 12 May 2026.
- Which products and versions are affected?
- snorkel (PyPI) ECOSYSTEM:introduced=0,last_affected=0.10.0.
- Is there a fix for CVE-2026-31224?
- 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-31224 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-31224?
- Check whether you run snorkel (PyPI) or Snorkel 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
The Snorkel library (up to and including v0.10.0) contains an insecure deserialization vulnerability (CWE-502) within the MultitaskClassifier.load() method. The root cause is the use of the torch.load() function without the weights_only=True parameter, which defaults to using the Pickle module for deserialization. An attacker can craft a malicious model file containing arbitrary Python objects that execute code upon being unpickled. Exploitation requires a user to load the malicious file using the affected method. As of the advisory date, no patched version is specified.
Affected products
- snorkel-team snorkel <= 0.10.0
Identifiers
- CVE-2026-31224
- GHSA-gpx5-7xm4-229w
- PYSEC-2026-3070
Timeline
- 2026-05-12: disclosed: Initial disclosure and NVD publication
- 2026-05-12: advisory: GitHub Advisory published
- 2026-05-18: other: GitHub Advisory reviewed and updated