How severe is GHSA-6m2c-76ff-6vrf?

GHSA-6m2c-76ff-6vrf has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by GHSA-6m2c-76ff-6vrf?

GHSA-6m2c-76ff-6vrf affects the following packages: qiskit-terra (PyPI), qiskit (PyPI), qiskit (PyPI). Ecosystems affected: PyPI.

How do I fix GHSA-6m2c-76ff-6vrf?

No patched version of qiskit-terra has shipped for GHSA-6m2c-76ff-6vrf yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect GHSA-6m2c-76ff-6vrf in my PyPI dependencies?

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.

How do I mitigate GHSA-6m2c-76ff-6vrf if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-6m2c-76ff-6vrf?

O3 pinpoints whether GHSA-6m2c-76ff-6vrf is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-6m2c-76ff-6vrf actively exploited in the wild?

No public exploit code has been indexed for GHSA-6m2c-76ff-6vrf yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-6m2c-76ff-6vrf?

GHSA-6m2c-76ff-6vrf has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 50th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-6m2c-76ff-6vrf?

GHSA-6m2c-76ff-6vrf is classified as Deserialization of Untrusted Data (CWE-502). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-6m2c-76ff-6vrf published, and has it been updated?

GHSA-6m2c-76ff-6vrf was published on March 14, 2025 and was last updated on May 2, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐍 PyPI

GHSA-6m2c-76ff-6vrf

CRITICAL

Qiskit allows arbitrary code execution decoding QPY format versions < 13

Also known asCVE-2025-2000

Published

Mar 14, 2025

Updated

May 2, 2025

Affected

3 pkgs

Patched

2 / 3

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk50th percentile+0.57%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

3 pkgs affected

🐍qiskit-terra🐍qiskit🐍qiskit

Real-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

Impact

A maliciously crafted QPY file can potentially execute arbitrary-code embedded in the payload without privilege escalation when deserializing QPY formats < 13. A python process calling Qiskit's qiskit.qpy.load() function could potentially execute any arbitrary Python code embedded in the correct place in the binary file as part of a specially constructed payload.

Patches

Fixed in Qiskit 1.4.2 and in Qiskit 2.0.0rc2

Affected Packages

3 total 2 fixed

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 dependency

Detect
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 GHSA-6m2c-76ff-6vrf 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 GHSA-6m2c-76ff-6vrf 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 GHSA-6m2c-76ff-6vrf. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Impact A maliciously crafted QPY file can potentially execute arbitrary-code embedded in the payload without privilege escalation when deserializing QPY formats < 13. A python process calling Qiskit's `qiskit.qpy.load()` function could potentially execute any arbitrary Python code embedded in the correct place in the binary file as part of a specially constructed payload. ### Patches Fixed in Qiskit 1.4.2 and in Qiskit 2.0.0rc2

O3 Security · Impact-Aware SCA

Is GHSA-6m2c-76ff-6vrf in your dependencies?

O3 detects GHSA-6m2c-76ff-6vrf across PyPI dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works