CVE-2025-2000: CWE-502 Deserialization of Untrusted Data in IBM Qiskit SDK
A maliciously crafted QPY file can potential execute arbitrary-code embedded in the payload without privilege escalation when deserialising QPY formats < 13. A python process calling Qiskit 0.18.0 through 1.4.1's `qiskit.qpy.load()` function could potentially execute any arbitrary Python code embedded in the correct place in the binary file as part of specially constructed payload.
AI Analysis
Technical Summary
CVE-2025-2000 identifies a critical security vulnerability in IBM's Qiskit SDK, a widely used open-source quantum computing framework. The vulnerability arises from unsafe deserialization practices in the qiskit.qpy.load() function when handling QPY files with format versions below 13. QPY files are binary serialization formats used to store quantum circuits and related data. The flaw allows an attacker to craft a malicious QPY file containing embedded Python code that executes arbitrarily when deserialized by the vulnerable function. This occurs without requiring any privilege escalation, user interaction, or authentication, making exploitation straightforward if the malicious file is loaded. The vulnerability is classified under CWE-502 (Deserialization of Untrusted Data), a common and dangerous security issue that can lead to remote code execution. The CVSS v3.1 base score of 9.8 reflects the critical nature of this flaw, with network attack vector, low attack complexity, no privileges required, and no user interaction needed. The impact spans confidentiality, integrity, and availability, as arbitrary code execution can lead to data theft, system compromise, or denial of service. The affected versions are specifically Qiskit SDK 0.18.0 through 1.4.1, with the vulnerability fixed in later releases. No public exploits have been reported yet, but the high severity demands immediate attention from organizations using these versions. The vulnerability highlights the risks inherent in deserializing untrusted inputs in quantum computing software, an emerging area with increasing adoption.
Potential Impact
The impact of CVE-2025-2000 is significant for organizations utilizing IBM's Qiskit SDK for quantum computing development, research, or production environments. Successful exploitation enables attackers to execute arbitrary Python code remotely without authentication or user interaction, potentially leading to full system compromise. This can result in theft or manipulation of sensitive quantum algorithms, intellectual property, or research data. Additionally, attackers could disrupt quantum computing workflows, causing denial of service or sabotage of experiments. Since Qiskit is used globally in academia, industry, and government research labs, the vulnerability poses a broad risk to the confidentiality, integrity, and availability of quantum computing resources. The ease of exploitation and lack of required privileges increase the likelihood of attacks once exploit code becomes available. Organizations relying on Qiskit for critical quantum applications or integrating it into larger software stacks must consider this vulnerability a high priority threat. The potential for lateral movement or pivoting from compromised quantum computing environments to other network assets also exists, amplifying the overall risk.
Mitigation Recommendations
To mitigate CVE-2025-2000, organizations should immediately cease loading QPY files from untrusted or unauthenticated sources in affected Qiskit versions (0.18.0 through 1.4.1). Until patches or updated versions are available, implement strict file validation and sandboxing measures to isolate the deserialization process. Employ application whitelisting and runtime monitoring to detect anomalous Python code execution during QPY file loading. Upgrade to the latest Qiskit SDK versions where this vulnerability has been addressed as soon as official patches are released. Additionally, conduct thorough code reviews and security testing of any custom extensions or integrations that utilize QPY deserialization. Educate developers and users about the risks of deserializing untrusted data and enforce policies restricting the use of unverified QPY files. Network segmentation and least privilege principles should be applied to limit the impact of potential exploitation. Finally, maintain up-to-date threat intelligence to detect any emerging exploits targeting this vulnerability.
Affected Countries
United States, China, Germany, Japan, South Korea, Canada, United Kingdom, France, Australia, Israel
CVE-2025-2000: CWE-502 Deserialization of Untrusted Data in IBM Qiskit SDK
Description
A maliciously crafted QPY file can potential execute arbitrary-code embedded in the payload without privilege escalation when deserialising QPY formats < 13. A python process calling Qiskit 0.18.0 through 1.4.1's `qiskit.qpy.load()` function could potentially execute any arbitrary Python code embedded in the correct place in the binary file as part of specially constructed payload.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2025-2000 identifies a critical security vulnerability in IBM's Qiskit SDK, a widely used open-source quantum computing framework. The vulnerability arises from unsafe deserialization practices in the qiskit.qpy.load() function when handling QPY files with format versions below 13. QPY files are binary serialization formats used to store quantum circuits and related data. The flaw allows an attacker to craft a malicious QPY file containing embedded Python code that executes arbitrarily when deserialized by the vulnerable function. This occurs without requiring any privilege escalation, user interaction, or authentication, making exploitation straightforward if the malicious file is loaded. The vulnerability is classified under CWE-502 (Deserialization of Untrusted Data), a common and dangerous security issue that can lead to remote code execution. The CVSS v3.1 base score of 9.8 reflects the critical nature of this flaw, with network attack vector, low attack complexity, no privileges required, and no user interaction needed. The impact spans confidentiality, integrity, and availability, as arbitrary code execution can lead to data theft, system compromise, or denial of service. The affected versions are specifically Qiskit SDK 0.18.0 through 1.4.1, with the vulnerability fixed in later releases. No public exploits have been reported yet, but the high severity demands immediate attention from organizations using these versions. The vulnerability highlights the risks inherent in deserializing untrusted inputs in quantum computing software, an emerging area with increasing adoption.
Potential Impact
The impact of CVE-2025-2000 is significant for organizations utilizing IBM's Qiskit SDK for quantum computing development, research, or production environments. Successful exploitation enables attackers to execute arbitrary Python code remotely without authentication or user interaction, potentially leading to full system compromise. This can result in theft or manipulation of sensitive quantum algorithms, intellectual property, or research data. Additionally, attackers could disrupt quantum computing workflows, causing denial of service or sabotage of experiments. Since Qiskit is used globally in academia, industry, and government research labs, the vulnerability poses a broad risk to the confidentiality, integrity, and availability of quantum computing resources. The ease of exploitation and lack of required privileges increase the likelihood of attacks once exploit code becomes available. Organizations relying on Qiskit for critical quantum applications or integrating it into larger software stacks must consider this vulnerability a high priority threat. The potential for lateral movement or pivoting from compromised quantum computing environments to other network assets also exists, amplifying the overall risk.
Mitigation Recommendations
To mitigate CVE-2025-2000, organizations should immediately cease loading QPY files from untrusted or unauthenticated sources in affected Qiskit versions (0.18.0 through 1.4.1). Until patches or updated versions are available, implement strict file validation and sandboxing measures to isolate the deserialization process. Employ application whitelisting and runtime monitoring to detect anomalous Python code execution during QPY file loading. Upgrade to the latest Qiskit SDK versions where this vulnerability has been addressed as soon as official patches are released. Additionally, conduct thorough code reviews and security testing of any custom extensions or integrations that utilize QPY deserialization. Educate developers and users about the risks of deserializing untrusted data and enforce policies restricting the use of unverified QPY files. Network segmentation and least privilege principles should be applied to limit the impact of potential exploitation. Finally, maintain up-to-date threat intelligence to detect any emerging exploits targeting this vulnerability.
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- ibm
- Date Reserved
- 2025-03-05T16:10:36.949Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6883ae32ad5a09ad00530b6b
Added to database: 7/25/2025, 4:17:54 PM
Last enriched: 2/27/2026, 12:01:45 AM
Last updated: 3/24/2026, 7:45:39 PM
Views: 270
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.