Skip to main content

CVE-2025-1403: CWE-502 Deserialization of Untrusted Data in IBM Qiskit SDK

High
VulnerabilityCVE-2025-1403cvecve-2025-1403cwe-502
Published: Fri Feb 21 2025 (02/21/2025, 16:55:03 UTC)
Source: CVE Database V5
Vendor/Project: IBM
Product: Qiskit SDK

Description

Qiskit SDK 0.45.0 through 1.2.4 could allow a remote attacker to cause a denial of service using a maliciously crafted QPY file containing a malformed symengine serialization stream which can cause a segfault within the symengine library.

AI-Powered Analysis

AILast updated: 08/27/2025, 00:36:03 UTC

Technical Analysis

CVE-2025-1403 is a high-severity vulnerability affecting IBM's Qiskit SDK versions from 0.45.0 through 1.2.4. The vulnerability arises from improper deserialization of untrusted data, specifically within the handling of QPY files that contain a malformed symengine serialization stream. QPY files are used to serialize quantum circuits in Qiskit, and the symengine library is a symbolic manipulation library used internally by Qiskit. When a maliciously crafted QPY file is processed, the malformed symengine serialization stream can trigger a segmentation fault (segfault) in the symengine library, leading to a denial of service (DoS) condition. This vulnerability is classified under CWE-502, which concerns unsafe deserialization of untrusted data. The CVSS v3.1 score is 8.6, indicating a high severity level, with an attack vector that is network-based (AV:N), requiring no privileges (PR:N) and no user interaction (UI:N). The scope is changed (S:C), meaning the vulnerability affects resources beyond the vulnerable component, and the impact is specifically on availability (A:H) with no impact on confidentiality or integrity. No known exploits are currently reported in the wild, and no patches have been linked yet. The vulnerability could be exploited remotely by an attacker sending a malicious QPY file to a system running a vulnerable Qiskit SDK version, causing the application or service to crash due to the segfault in symengine, resulting in denial of service. Since Qiskit is a quantum computing SDK primarily used by researchers, developers, and organizations working on quantum computing projects, the attack surface is somewhat specialized but critical for those environments.

Potential Impact

For European organizations engaged in quantum computing research, development, or deployment using IBM's Qiskit SDK, this vulnerability poses a significant risk of service disruption. A successful exploitation could cause denial of service in quantum computing applications or services that rely on Qiskit, potentially halting research workflows, delaying development projects, or interrupting critical quantum simulations. This could impact academic institutions, research labs, and companies involved in quantum technology innovation. Although the vulnerability does not directly compromise data confidentiality or integrity, the availability impact could lead to operational downtime and loss of productivity. Given the specialized nature of quantum computing, affected organizations may face challenges in quickly recovering from such disruptions due to the complexity and niche expertise required. Additionally, as quantum computing gains strategic importance in Europe for technological leadership and national security, disruptions could have broader implications on competitiveness and innovation timelines.

Mitigation Recommendations

1. Immediate mitigation involves upgrading the Qiskit SDK to a version beyond 1.2.4 once IBM releases a patched version addressing CVE-2025-1403. Until a patch is available, organizations should avoid processing untrusted or unauthenticated QPY files, especially those received from external or unverified sources. 2. Implement strict input validation and sandboxing for any components that deserialize QPY files to contain potential crashes and prevent system-wide impact. 3. Employ network-level controls such as firewalls and intrusion detection/prevention systems to monitor and block suspicious traffic that could deliver malicious QPY files. 4. For environments where Qiskit is exposed via APIs or web services, enforce authentication and authorization to restrict access to trusted users only, reducing the risk of remote exploitation. 5. Establish monitoring and alerting for application crashes or abnormal behavior in systems running Qiskit to enable rapid detection and response to potential exploitation attempts. 6. Educate developers and users of Qiskit within the organization about the risks of deserializing untrusted data and promote secure coding and handling practices for quantum computing workflows.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.1
Assigner Short Name
ibm
Date Reserved
2025-02-17T19:37:50.068Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 689a2234ad5a09ad00274f05

Added to database: 8/11/2025, 5:02:44 PM

Last enriched: 8/27/2025, 12:36:03 AM

Last updated: 9/25/2025, 9:49:34 PM

Views: 46

Actions

PRO

Updates to AI analysis are available only with a Pro account. Contact root@offseq.com for access.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats