No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 15 May 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 13 May 2026 17:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Critical Insecure Deserialization in Snorkel BaseLabeler |
Wed, 13 May 2026 15:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Snorkel
Snorkel snorkel |
|
| CPEs | cpe:2.3:a:snorkel:snorkel:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Snorkel
Snorkel snorkel |
|
| Metrics |
cvssV3_1
|
Tue, 12 May 2026 18:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Critical Insecure Deserialization in Snorkel BaseLabeler | |
| Weaknesses | CWE-502 |
Tue, 12 May 2026 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| References |
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2026-05-15T18:05:33.607Z
Reserved: 2026-03-09T00:00:00.000Z
Link: CVE-2026-31223
Updated: 2026-05-15T17:23:35.514Z
Status : Modified
Published: 2026-05-12T16:16:14.223
Modified: 2026-05-15T19:16:57.800
Link: CVE-2026-31223
No data.
OpenCVE Enrichment
Updated: 2026-05-13T17:30:06Z