# CVE-2026-31223: Snorkel BaseLabeler.load uses an unsafe pickle.load

> A remote attacker can execute arbitrary code by providing a malicious pickle file to the BaseLabeler.load method in the snorkel library.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 15 May 2026
- **Also known as:** GHSA-fq92-qc8f-482v, PYSEC-2026-3069

## What is CVE-2026-31223?

CVE-2026-31223 is a high-severity unsafe deserialization vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The snorkel library thru v0.10.0 contains a critical insecure deserialization vulnerability (CWE-502) in the BaseLabeler.load() method of the BaseLabeler class. The method loads serialized labeler models using the unsafe pickle.load() function on user-supplied file paths without any validation or security controls. Python's pickle module is inherently dangerous for deserializing untrusted data, as it can execute arbitrary code during the deserialization process. A remote attacker can exploit this by providing a maliciously crafted pickle file, leading to arbitrary code execution on the victim's system when the file is loaded via the vulnerable method.

Weakness: CWE-502 (Deserialization of Untrusted Data)

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

3 open source packages ship an affected version, including snorkel. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `snorkel` | PyPI | All versions to 0.10.0 | None |
| `snorkel` | PyPI | All versions to 0.10.0 | None |
| `snorkel` | PyPI | All versions to 0.10.0 | None |

Products: Snorkel Snorkel.

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

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

## Is CVE-2026-31223 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2026-31222](https://insights.sbomify.com/CVE-2026-31222/): Snorkel Trainer.load uses an unsafe torch.load (high 8.8)
- [CVE-2026-31224](https://insights.sbomify.com/CVE-2026-31224/): Snorkel MultitaskClassifier.load uses an unsafe torch.load (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-31223 is a high-severity unsafe deserialization vulnerability in n/a, published on 12 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-31223 in the wild and no public exploit code.

Affected packages and fixed versions:
- snorkel (PyPI): affected all versions up to 0.10.0; no fix listed
- snorkel (PyPI): affected all versions up to 0.10.0; no fix listed
- snorkel (PyPI): affected all versions up to 0.10.0; 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-31223/ (Markdown: https://insights.sbomify.com/CVE-2026-31223/index.md)
```

## Sources

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

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