Skip to content
High-Risk CVE-2026-120833: Deserialization Vulnerability in Labbench

High-Risk CVE-2026-120833: Deserialization Vulnerability in Labbench

First seen 3 Nov 2026, 12:12 UTC • •
API

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •November 3, 2026 at 17:17 UTC
  • •CVE-2026-120833 affects labbench versions before 0.46.1, allowing arbitrary code execution.
  • •Research teams using Python-based workflows are particularly vulnerable to this flaw.
  • •Immediate upgrades to the patched version are essential to mitigate risks.

A high-risk vulnerability, CVE-2026-120833, has been identified in labbench versions prior to 0.46.1. This flaw allows deserialization of untrusted data through the read() and read_relational() functions, enabling attackers to execute arbitrary code via crafted .p or .pickle files. Affected users include research and engineering teams utilizing Python-based data workflows, especially those processing files from external sources. The exploitation method requires user interaction to load the malicious file, which can lead to full compromise of the user's process. No proof-of-concept or active exploitation has been confirmed yet. Immediate upgrades to the fixed version are recommended to mitigate risks. The vulnerability was published on November 3, 2026, with a CVSS score of 8.5, indicating a high severity level.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-11-03
CVE-2026-120833 published
The vulnerability was disclosed with a CVSS score of 8.5, highlighting its high risk.
Redpacketsecurity

More articles in this cluster (6)

Following this threat?

Track CVE-2026-120833 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Extracted Entities (4)

1 / 4

Common questions

What versions of labbench are affected?
Labbench versions prior to 0.46.1 are affected by CVE-2026-120833.
How can I mitigate this vulnerability?
Upgrade to labbench version 0.46.1 or later to mitigate the vulnerability.
Is there any active exploitation of this CVE?
No active exploitation has been reported as of now, but the risk remains high.