CVE-2025-2000
CRITICALCVE-2025-2000 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in qiskit-terra. O3 Security confirms whether CVE-2025-2000 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Qiskit allows arbitrary code execution decoding QPY format versions < 13
Real-World Exposure
qiskit-terra🐍qiskit🐍qiskitReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects PyPI packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐍PyPI | qiskit-terra | ≥ 0.18.0 | No fix |
| 🐍PyPI | qiskit | all versions | 1.4.2 |
| 🐍PyPI | qiskit | ≥ 2.0.0rc1&&< 2.0.0rc2 | 2.0.0rc2 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for qiskit-terra. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
No patched version of qiskit-terra has shipped for CVE-2025-2000 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether CVE-2025-2000 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2025-2000. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2025-2000 in your dependencies?
O3 detects CVE-2025-2000 across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.