Cyber Resilience

CVE-2025-2000

RCE in Ibm Qiskit 0.18.0 – 1.4.2

Published
14 March 2025
Modified
18 August 2025
Patch / advisory
CVSS Score v3.1 9.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0079 53th percentile
Risk Priority 72 floored blend · peak EPSS

Summary

CVE-2025-2000 is a critical-severity Deserialization of Untrusted Data (CWE-502) vulnerability in Ibm Qiskit. Its CVSS base score is 9.8 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 47% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-2000 is a critical deserialization vulnerability (CWE-502) affecting the Qiskit quantum computing framework, specifically versions 0.18.0 through 1.4.1. The flaw resides in the `qiskit.qpy.load()` function, which processes QPY binary files in formats less than version 13. A maliciously crafted QPY file can embed arbitrary Python code that executes during deserialization without requiring privilege escalation. The vulnerability carries a CVSS v3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) and was published on 2025-03-14.

The attack scenario involves remote attackers with no privileges or user interaction, who can supply a specially constructed QPY payload to any Python process invoking the vulnerable `qiskit.qpy.load()` function. Successful exploitation allows execution of arbitrary Python code embedded in the file, enabling full compromise of the affected process with high impact on confidentiality, integrity, and availability.

Mitigation details are available in the IBM support advisory at https://www.ibm.com/support/pages/node/7185949.

OWASP Top 10 for Web (2025)

EU & UK References

Vulnerability Data

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…

more

in the correct place in the binary file as part of specially constructed payload.

CWE(s)

Related Threats

MITRE ATT&CK Enterprise Techniques

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-1403Same product: Ibm Qiskit
CVE-2026-14974Same vendor: Ibm
CVE-2024-31903Same vendor: Ibm
CVE-2026-12118Same vendor: Ibm
CVE-2024-43191Same vendor: Ibm
CVE-2019-4279Same vendor: Ibm
CVE-2023-24971Same vendor: Ibm
CVE-2025-36072Same vendor: Ibm
CVE-2020-4888Same vendor: Ibm
CVE-2024-29032Same vendor: Ibm

Affected Assets

ibm
qiskit
0.18.0 — 1.4.2

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

Developer testing and evaluation can uncover deserialization flaws before deployment.

Input validation directly stops deserialization of untrusted data by ensuring inputs are valid before processing.

Engineering principles such as safe deserialization and input sanitization structurally prevent the weakness from being introduced.

Integrity verification tools can detect malformed or tampered serialized data after the fact.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-02 none match
prevents

PR.PS-02 addresses only post-deployment updates/patching and cannot prevent introduction of unsafe deserialization code, yet it can remediate some instances when the flaw exists in outdated libraries or components.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

finds

Security testing includes validation of deserialization routines and the use of untrusted data, reducing the likelihood that unsafe object reconstruction will be deployed.

prevents

Requiring vetted libraries, regular updates and SAST before release reduces the likelihood that deserialization logic will accept and act on attacker-controlled serialized objects.

finds

Regular scanning of third-party libraries and timely patching reduce the likelihood that unsafe deserialization vulnerabilities remain active.

none

Mandatory malware scanning of data received over networks or storage media intercepts malicious serialized payloads before they are deserialized by the target application.

References