Live › vulnerability › CVE-2026-120833
labbench before 0.46.1 passes any file ending in .p or .pickle to pandas.read_pickle based on the extension alone, in its read() and read_relational() functions. An attacker who supplies a crafted data file or relational data archive can run arbitrary code when a user loads it.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 01:47 UTC. All times on this page are UTC.
Teams that load data files with labbench's read() or read_relational() functions, especially files from outside their own organisation. Code that only reads data it generated itself is much less exposed. unknown whether the sources list other exposure conditions.
No product ranges from the sources yet.
pip show labbench and confirm whether it is below 0.46.1.labbench read() or read_relational() on files supplied by others.0.46.1 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2026-120833")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.