CVE-2025-2000GHSA-6M2C-76FF-6VRFPYSEC-2026-510PYSEC-2026-511
Qiskit SDK code execution
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 1.4.2, 2.0.0rc2
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
CISA's decision points: whether it is exploited, whether attacks can be automated, and how much control an attacker gets. Assessed (SSVC 2.0.3).What do these mean? →
- Exploitation: none
- Automatable: yes
- Technical impact: total
Summary
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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: total
- Record last updated
Affected versions
- IBM Qiskit SDK
From 0.18.0 · through 1.4.1
- qiskit-terraPyPI
From 0.18.0 · through 0.46.3
- qiskitPyPI
fixed in 1.4.2
- qiskitPyPI
From 2.0.0rc1 · fixed in 2.0.0rc2
- qiskitPyPI
fixed in 1.4.2; From 2.0.0rc1 · fixed in 2.0.0rc2