CVE-2025-2000: A maliciously crafted QPY file can potential execute arbitrary-code embedded in the payload without privilege

Q: How urgent is CVE-2025-2000?

Priority 54/100. Critical severity; Remotely exploitable, no login, no user action

This month

CRITICAL 9.8REMOTEUPGRADE

CVE-2025-2000 is a critical-severity flaw (CVSS 9.8) affecting qiskit. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Remotely exploitable, no login, no user action

A fixed release or distro patch exists.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	0.8% (top 43%)
CISA exploited list	No
Weakness	CWE-502
Published	2025-03-14
Last modified	2026-06-17

Publisher (CNA): IBM Corporation · Vendor: ibm

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2025-03-14 13:15 UTCPublished CVE record published
2026-06-17 09:06 UTCUpdated Record last modified

ibm qiskit UPGRADE

Affected: >= 0.18.0 and < 1.4.2

Fixed in: 1.4.2

Safe to downgrade to: a release before 0.18.0

1. Check installed version

apt-cache policy qiskit || rpm -q qiskit || qiskit --version

2. UPGRADE to 1.4.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade qiskit

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade qiskit

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 0.18.0 (Debian / Ubuntu)

apt-cache madison qiskit sudo apt install qiskit=<VERSION_BEFORE_0.18.0> sudo apt-mark hold qiskit

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list qiskit sudo dnf downgrade qiskit-<VERSION_BEFORE_0.18.0> sudo dnf versionlock add qiskit

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-2000?

qiskit: upgrade to 1.4.2. Exact commands for each OS are on this page.

Is CVE-2025-2000 being exploited?

CVE-2025-2000 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-2000 affect?

CVE-2025-2000 affects qiskit. Severity is critical (CVSS 9.8). 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()` functio

How urgent is CVE-2025-2000?

Priority 54/100. Critical severity; Remotely exploitable, no login, no user action

Software pages

Python vulnerabilities

Related CVEs

CVE-2025-1403 HIGH 8.6 UPGRADE Qiskit SDK 0.45.0 through 1.2.4 could allow a remote attacker to cause a denial of service using a maliciously

References

← Back to latest CVEs