{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-7584 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-7584 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-7584 is a high-severity unsafe deserialization vulnerability in Zurich Instruments LabOne Q, published on 1 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-7584 and fix it if it is affected.\n\nWhat it is: CVE-2026-7584 is a high-severity unsafe deserialization vulnerability in Zurich Instruments LabOne Q, published on 1 May 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-7584 in the wild and no public exploit code.\n\nAffected product: Zurich Instruments LabOne Q. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-7584/ (Markdown: https://insights.sbomify.com/CVE-2026-7584/index.md)","id":"CVE-2026-7584","markdown":"https://insights.sbomify.com/CVE-2026-7584/index.md","name":"CVE-2026-7584","record":{"aliases":["GHSA-h9hw-pgfp-h6xc"],"analysis":{"component_type":"library","fix_type":"patch","impacts":["code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"LabOne Q Python library","requires_auth":"none","summary":"Attackers can execute arbitrary code by tricking users into loading malicious experiment files in the LabOne Q Python library.","user_interaction":"required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"NCSC.ch","cpe":[{"product":"labone_q","vendor":"zhinst"}],"cvss":{"score":8.4,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Arbitrary Code Execution via Unsafe Deserialization in LabOne Q","id":"CVE-2026-7584","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"Open5GS AMF nudm-handler.c amf_nudm_sdm_handle_provisioned denial of service","id":"CVE-2026-7585"},"packages":[],"prev":{"headline":"Open5GS BSF context.c bsf_sess_find_by_ipv6prefix denial of service","id":"CVE-2026-7583"},"products":["LabOne Q"],"published":"2026-05-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-05-01","vendors":["Zurich Instruments"]},"summary":"Attackers can execute arbitrary code by tricking users into loading malicious experiment files in the LabOne Q Python library.","url":"https://insights.sbomify.com/CVE-2026-7584/"}