Unsafe Deserialization in LabOne Q Serialization Framework

The LabOne Q serialization framework uses a class-loading mechanism (import_cls) to dynamically import and instantiate Python classes during deserialization. Prior to the fix, this mechanism accepted arbitrary fully-qualified class names from the serialized data without any validation of the target class or restriction on which modules could be imported. An attacker can craft a serialized experiment file that causes the deserialization engine to import and instantiate arbitrary Python classes with attacker-controlled constructor arguments, resulting in arbitrary code execution in the context of the user running the Python process. Exploitation requires the victim to load a malicious file using LabOne Q's deserialization functions, for example a compromised experiment file shared for collaboration or support purposes.

Casky was already ahead

This CVE exploits attack patterns that Casky's 419matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

CVE-2026-7584 represents a critical unsafe deserialization vulnerability in the LabOne Q serialization framework, specifically within its class-loading mechanism (import_cls) that dynamically imports Python classes during deserialization. The vulnerability allows attackers to craft malicious serialized experiment files that bypass validation controls, enabling arbitrary code execution through instantiation of unintended classes from any accessible Python module. This affects researchers, engineers, and organizations using LabOne Q for quantum computing experiments, where serialized files are commonly exchanged, loaded, and processed as part of routine workflows. The 7.8 CVSS score reflects the high severity of unauthenticated remote code execution possible through simple file delivery mechanisms.

Casky's 419 matching security skills leverage Claude AI's extended reasoning to correlate this vulnerability across MITRE ATT&CK Initial Access (TA0001), Execution (TA0043), and Persistence (TA0002) techniques. Practitioners using Casky would detect attack patterns including: (1) Initial Access attempts via malicious serialized .qo or experiment files delivered through email or repositories; (2) Execution through the deserialization engine's automatic class instantiation without whitelist validation; and (3) Persistence mechanisms where attacker-controlled classes establish backdoors during import. The platform's CWE-502 mapping (Deserialization of Untrusted Data) connects to defensive controls like input validation during deserialization, restricting importable modules, implementing object whitelisting, and monitoring for suspicious class-loading behavior—enabling practitioners to identify both attack indicators and remediation priorities within their LabOne Q deployments.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

419 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-7584.

analyzing-android-malware-with-apktool

malware analysis · medium

Run

analyzing-apt-group-with-mitre-navigator

threat intelligence · low

Run

analyzing-bootkit-and-rootkit-samples

malware analysis · medium

Run

MITRE ATT&CK Techniques

TA0001 TA0043 TA0002

Investigate the attack patterns behind CVE-2026-7584

Casky has 419 skills that investigate the attack patterns behind CVE-2026-7584. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn