← Back
CVE-2025-2000

Unsafe Deserialization in qiskit-terra (CVE-2025-2000)

Summary

vulnerability in qiskit-terra (CVE-2025-2000). Successful exploitation can lead to full system takeover. Mitigation: upgrade to `1.4.2, 2.0.0rc2` or later.

AI summary snake-internal / snake-material-v2

A vulnerability tracked as **CVE-2025-2000** has been found in qiskit-terra. Successful exploitation can lead to full system takeover. CVSS score: ?/10. What to do: upgrade qiskit-terra to **1.4.2, 2.0.0rc2** or later. If unsure, ask your IT team or search "qiskit-terra CVE-2025-2000" on the vendor's site.
CVE-2025-2000 (qiskit-terra) — CWE-502 / Attack vector: remote (network-reachable) / unauthenticated / no user interaction Patched: `1.4.2, 2.0.0rc2` — apply immediately Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs. Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**unsafe deserialization** (CWE-502) exists in qiskit-terra.
📍 Affected scope
qiskit-terra — .
🔥 Severity
Severity: ?. Successful exploitation can lead to full system takeover
🔧 How to fix
Update to **1.4.2, 2.0.0rc2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'qiskit-terra' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response Actions (7 steps)

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify
    grep -r 'qiskit-terra' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `qiskit-terra` を grep し、稼働しているサービス・バージョンを把握する。

  2. 6
    Apply patch patch
    Upgrade qiskit-terra to 1.4.2, 2.0.0rc2

    ステージング環境で 1.4.2, 2.0.0rc2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。

  3. 7
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

PyPI qiskit-terra
[{"type":"ECOSYSTEM","events":[{"introduced":"0.18.0"},{"last_affected":"0.46.3"}]}]
PyPI qiskit
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.4.2"},{"introduced":"2.0.0rc1"},{"fixed":"2.0.0rc2"}]}]

References

🍪 About cookies

We use cookies to keep you logged in, remember your language, and improve the service.

Details →