Snorkel MultitaskClassifier.load uses an unsafe torch.load

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-31224: 0.39% estimated exploitation activity in the next 30 days; percentile 33.43 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The snorkel library thru v0.10.0 contains an insecure deserialization vulnerability (CWE-502) in the MultitaskClassifier.load() method of the MultitaskClassifier class. The method loads model weight files using torch.load() without enabling the security-restrictive weightsonly=True parameter. This default behavior allows the deserialization of arbitrary Python objects via the Pickle module. A remote attacker can exploit this by providing a maliciously crafted model file, leading to arbitrary code execution on the victim's system when the file is loaded via the vulnerable method.

Published by the source

12 May 2026, 18:30 UTC

Last modified by the source

13 Jul 2026, 16:42 UTC

Source last checked

26 Oct 2026, 13:41 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-gpx5-7xm4-229w

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-gpx5-7xm4-229w

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-31224

Advisory: Snorkel MultitaskClassifier.load uses an unsafe torch.load
IDs: CVE-2026-31224, GHSA-gpx5-7xm4-229w
Record: https://patchnext.com/advisories/cve-2026-31224 (revision 2, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI snorkel: affected <= 0.10.0

## Suggested inspection (read-only)
- `python -m pip show snorkel`: prints the installed version. Run with the environment that serves production active.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on snorkel.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-gpx5-7xm4-229w (OSV record GHSA-gpx5-7xm4-229w lists affected ranges: PyPI snorkel >=0 <=0.10.0)
- Verified: https://github.com/advisories/GHSA-gpx5-7xm4-229w (GitHub-reviewed advisory GHSA-gpx5-7xm4-229w lists affected ranges: PyPI snorkel >=0 <=0.10.0)

Commands are suggestions: review each one before running it.