CVE-2026-31223
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe snorkel library v0.10.0 and earlier contains an insecure deserialization vulnerability (CWE-502) in the BaseLabeler.load() method. This method uses Python's pickle.load() function to deserialize labeler models from user-supplied file paths without any validation or security controls, allowing attackers to execute arbitrary code by providing malicious pickle files.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data<= 0.10.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check if snorkel is installed and identify its versionRun: pip show snorkel or pip list | grep snorkel to see the installed version numberAffected if The installed version is 0.10.0 or any version lower than it (e.g., 0.9.0, 0.8.0, etc.)
-
Search for usage of BaseLabeler.load() in your codebaseSearch your codebase for patterns like 'BaseLabeler.load(' or 'from snorkel.labeling import BaseLabeler' followed by '.load('Affected if Your code calls the BaseLabeler.load() method to load labeler models from files
-
Identify pickle file loading operationsSearch for pickle.load() calls in your code or in snorkel-related modules, particularly those that load from user-supplied file pathsAffected if Your application uses pickle.load() to deserialize labeler models from files without validation
-
Check if labeler model files are loaded from untrusted sourcesReview how labeler model files are obtained - check if they come from user uploads, external URLs, or other untrusted locationsAffected if Labeler model files are loaded from sources that could be controlled by attackers (e.g., user uploads, remote URLs)
You are affected if you have snorkel version 0.10.0 or lower installed AND your code uses BaseLabeler.load() to deserialize labeler models from files that could be maliciously crafted.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataReplace pickle.load() with a safe deserialization approach (e.g., JSON, pickle with signed/encrypted data, or a safer library like cloudpickle with strict controls), and add validation to verify the source and integrity of any loaded files before deserialization.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31223 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-31223 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data