CVE-2026-120833
Received Received - Intake

labbench Deserialization of Untrusted Data Vulnerability

Vulnerability report for CVE-2026-120833, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-11-03

Last updated on: 2026-11-03

Assigner: VulnCheck

Description

labbench before 0.46.1 contains a deserialization of untrusted data vulnerability in read() and read_relational() that passes any file with a .p or .pickle extension to pandas.read_pickle based on the extension alone. Attackers who supply a crafted data file or relational data archive can execute arbitrary code when a user loads it with these functions.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-11-03
Last Modified
2026-11-03
Generated
2026-11-03
AI Q&A
2026-11-03
EPSS Evaluated
N/A
NVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
NIST labbench 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-502 The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects the labbench Python package before version 0.46.1. It involves a deserialization of untrusted data issue where the read() and read_relational() functions automatically pass files with .p or .pickle extensions to pandas.read_pickle without proper validation. Attackers can exploit this by providing a crafted file, leading to arbitrary code execution when a user loads it.

Detection Guidance

Check for files with .p or .pickle extensions in directories accessed by labbench. Use commands like 'find / -name "*.p" -o -name "*.pickle" 2>/dev/null' to locate such files. Verify if labbench version is below 0.46.1 with 'pip show labbench' or 'conda list labbench'.

Impact Analysis

If you use labbench versions before 0.46.1, an attacker could trick you into loading a malicious .p or .pickle file. This could allow the attacker to execute arbitrary code on your system, potentially leading to data theft, system compromise, or further network intrusions.

Mitigation Strategies

Upgrade labbench to version 0.46.1 or later. Set the environment variable LABBENCH_AUTOLOAD_PICKLE to a non-disabling value to restrict unsafe unpickling. Avoid loading untrusted .p or .pickle files.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-120833. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart

Security Radar

News mentioning this vulnerability
Loading related security news...