Code execution via malicious QPY deserialization
Published Mar 14, 2025 · Updated Feb 26, 2026
QPY deserialization in IBM Qiskit SDK 0.18.0 through 1.4.1 allows attackers to execute arbitrary Python code from crafted files. The qiskit.qpy.load() entry point decodes attacker-controlled executable content embedded in QPY format versions below 13 instead of treating it solely as data. Exploitation requires a process to load an attacker-supplied QPY file, after which the payload runs with that process's privileges.
Summary
What happened
QPY deserialization in IBM Qiskit SDK 0.18.0 through 1.4.1 allows attackers to execute arbitrary Python code from crafted files. The qiskit.qpy.load() entry point decodes attacker-controlled executable content embedded in QPY format versions below 13 instead of treating it solely as data. Exploitation requires a process to load an attacker-supplied QPY file, after which the payload runs with that process's privileges.
The record
- CVE
- CVE-2025-2000
- Published
- Mar 14, 2025
- Updated
- Feb 26, 2026
- Vendor
- IBM
- Product
- Qiskit SDK
- Classifications
- CWE-502, T1059.006
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 14, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.18.0 <=1.4.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo