CVE-2025-2000
IBM Qiskit insecure deserialization
- Published14 Mar 2025
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HAffected products
Remediation
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-2000 being actively exploited?
CVE-2025-2000 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.81%.
How severe is CVE-2025-2000?
CVE-2025-2000 has a CVSS 3.1 base score of 9.8, rated critical. EPSS estimates a 0.81% probability of exploitation.
Which products are affected by CVE-2025-2000?
Affected products include IBM Qiskit.
How do I fix CVE-2025-2000?
Upgrade affected software to a fixed version, for example IBM Qiskit 1.4.2 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-2000 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.