VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

qiskit: vulnerability history, versions and safety

qiskit is a package in the PyPI ecosystem. Vulert records 4 vulnerabilities for it across 120 releases, from Feb 2025 to Jul 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded C1 H1 U2
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 13 Jul 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all qiskit vulnerabilities

Vulert verdict on qiskit 2.6.1 i

Updated on 23 Oct 2026

Careful: 2.6.1 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.6.1 — affected i
  • Vulnerabilities on record 4 over 1 year · 2 in the last year i
  • Latest disclosure 13 Jul 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Stars 7,914 i
  • OpenSSF scorecard 6/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for qiskit, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
2.6.1 22 Oct 2026 C1 Apache-2.0 No Details →
2.6.0 16 Oct 2026 C1 Apache-2.0 No Details →
2.6.0rc1 02 Oct 2026 C1 Apache-2.0 No Details →
2.5.2 13 Aug 2026 C1 Apache-2.0 No Details →
2.5.1 23 Jul 2026 C1 Apache-2.0 No Details →
2.5.0 02 Jul 2026 C1 Apache-2.0 No Details →
2.5.0rc1 18 Jun 2026 C1 Apache-2.0 No Details →
2.4.2 12 Jun 2026 C1 Apache-2.0 No Details →
1.4.6 12 Jun 2026 C1 Apache-2.0 No Details →
2.4.1 24 Apr 2026 C1 Apache-2.0 No Details →
2.4.0 16 Apr 2026 C1 Apache-2.0 No Details →
2.4.0rc3 07 Apr 2026 C1 Apache-2.0 No Details →
2.4.0rc2 27 Mar 2026 C1 Apache-2.0 No Details →
2.4.0rc1 19 Mar 2026 C1 Apache-2.0 No Details →
2.3.1 13 Mar 2026 C1 Apache-2.0 No Details →
2.3.0 08 Jan 2026 C1 Apache-2.0 No Details →
2.3.0rc1 12 Dec 2025 C1 Apache-2.0 No Details →
2.2.3 30 Oct 2025 C1 Apache-2.0 No Details →
2.2.2 22 Oct 2025 C1 Apache-2.0 No Details →
1.4.5 13 Oct 2025 C1 Apache-2.0 No Details →
2.2.1 26 Sep 2025 C1 Apache-2.0 No Details →
2.2.0 18 Sep 2025 C1 Apache-2.0 No Details →
2.2.0rc1 04 Sep 2025 C1 Apache-2.0 No Details →
2.2.0b1 28 Aug 2025 C1 Apache-2.0 No Details →
2.1.2 19 Aug 2025 C1 Apache-2.0 No Details →
1.4.4 15 Aug 2025 C1 Apache-2.0 No Details →
2.1.1 10 Jul 2025 C1 Apache-2.0 No Details →
2.1.0 19 Jun 2025 C1 Apache-2.0 No Details →
2.0.3 17 Jun 2025 C1 Apache-2.0 No Details →
2.1.0rc1 05 Jun 2025 C1 Apache-2.0 No Details →
2.0.2 27 May 2025 C1 Apache-2.0 No Details →
2.0.1 16 May 2025 C1 Apache-2.0 No Details →
1.4.3 12 May 2025 C1 Apache-2.0 No Details →
2.0.0 31 Mar 2025 C1 Apache-2.0 No Details →
2.0.0rc2 14 Mar 2025 C1 Apache-2.0 No Details →
1.4.2 14 Mar 2025 C1 Apache-2.0 No Details →
2.0.0rc1 10 Mar 2025 U1 Apache-2.0 Yes Details →
1.4.1 06 Mar 2025 C1 Apache-2.0 No Details →
1.4.0 21 Feb 2025 C1 Apache-2.0 No Details →
1.3.3 20 Feb 2025 C1 Apache-2.0 No Details →
1.3.2 20 Jan 2025 C1 Apache-2.0 No Details →
1.3.1 12 Dec 2024 C1 Apache-2.0 No Details →
1.3.0 28 Nov 2024 C1 Apache-2.0 No Details →
1.3.0rc2 20 Nov 2024 C1 H1 U1 Apache-2.0 No Details →
1.3.0rc1 07 Nov 2024 C1 H1 U1 Apache-2.0 No Details →
1.2.4 03 Oct 2024 C1 H1 U1 Apache-2.0 No Details →
1.2.3 02 Oct 2024 C1 H1 U1 Apache-2.0 No Details →
0.46.3 27 Sep 2024 C1 H1 U1 Apache-2.0 No Details →
1.2.2 20 Sep 2024 C1 H1 U1 Apache-2.0 No Details →
1.2.1 12 Sep 2024 C1 H1 U1 Apache-2.0 No Details →
1.3.0b1 11 Sep 2024 C1 H1 U1 Apache-2.0 No Details →
1.2.0 15 Aug 2024 C1 H1 U1 Apache-2.0 No Details →
1.1.2 09 Aug 2024 C1 H1 U1 Apache-2.0 No Details →
1.2.0rc1 01 Aug 2024 C1 H1 U1 Apache-2.0 No Details →
0.46.2 20 Jun 2024 C1 H1 U1 Apache-2.0 No Details →
1.1.1 20 Jun 2024 C1 H1 U1 Apache-2.0 No Details →
1.1.0 16 May 2024 C1 H1 U1 Apache-2.0 No Details →
1.1.0rc1 03 May 2024 C1 H1 U1 Apache-2.0 No Details →
0.46.1 08 Mar 2024 C1 H1 U1 Apache-2.0 No Details →
1.0.2 07 Mar 2024 C1 H1 U1 Apache-2.0 No Details →
1.0.1 22 Feb 2024 C1 H1 U1 Apache-2.0 No Details →
1.0.0 15 Feb 2024 C1 H1 U1 Apache-2.0 No Details →
1.0.0rc1 02 Feb 2024 C1 H1 U1 non-standard No Details →
0.46.0 01 Feb 2024 C1 H1 U1 Apache-2.0 No Details →
0.45.3 01 Feb 2024 C1 H1 U1 Apache-2.0 No Details →
0.45.2 18 Jan 2024 C1 H1 U1 Apache-2.0 No Details →
1.0.0b1 01 Dec 2023 C1 H1 U1 non-standard No Details →
0.45.1 29 Nov 2023 C1 H1 U1 Apache-2.0 No Details →
0.45.0 03 Nov 2023 C1 H1 U1 Apache-2.0 No Details →
0.44.3 25 Oct 2023 C1 Apache-2.0 No Details →
0.45.0rc1 19 Oct 2023 C1 Apache-2.0 No Details →
0.44.2 04 Oct 2023 C1 Apache-2.0 No Details →
0.44.1 17 Aug 2023 C1 Apache-2.0 No Details →
0.44.0 27 Jul 2023 C1 Apache-2.0 No Details →
0.43.3 19 Jul 2023 C1 Apache-2.0 No Details →
0.43.2 28 Jun 2023 C1 Apache-2.0 No Details →
0.43.1 04 Jun 2023 C1 Apache-2.0 No Details →
0.43.0 04 May 2023 C1 Apache-2.0 No Details →
0.42.1 21 Mar 2023 C1 Apache-2.0 No Details →
0.42.0 10 Mar 2023 C1 Apache-2.0 No Details →
0.41.1 24 Feb 2023 C1 Apache-2.0 No Details →
0.41.0 31 Jan 2023 C1 Apache-2.0 No Details →
0.40.0 26 Jan 2023 C1 Apache-2.0 No Details →
0.39.5 17 Jan 2023 C1 Apache-2.0 No Details →
0.39.4 08 Dec 2022 C1 Apache-2.0 No Details →
0.39.3 25 Nov 2022 C1 Apache-2.0 No Details →
0.39.2 04 Nov 2022 C1 Apache-2.0 No Details →
0.39.1 02 Nov 2022 C1 Apache-2.0 No Details →
0.39.0 13 Oct 2022 C1 Apache-2.0 No Details →
0.38.0 15 Sep 2022 C1 Apache-2.0 No Details →
0.37.2 23 Aug 2022 C1 Apache-2.0 No Details →
0.37.1 28 Jul 2022 C1 Apache-2.0 No Details →
0.37.0 30 Jun 2022 C1 Apache-2.0 No Details →
0.36.2 18 May 2022 C1 Apache-2.0 No Details →
0.36.1 21 Apr 2022 C1 Apache-2.0 No Details →
0.36.0 06 Apr 2022 C1 Apache-2.0 No Details →
0.35.0 31 Mar 2022 C1 Apache-2.0 No Details →
0.34.2 09 Feb 2022 C1 Apache-2.0 No Details →
0.34.1 05 Jan 2022 C1 Apache-2.0 No Details →
0.34.0 20 Dec 2021 C1 Apache-2.0 No Details →
0.33.1 10 Dec 2021 C1 — No Details →
0.33.0 06 Dec 2021 C1 — No Details →
0.32.1 22 Nov 2021 C1 — No Details →
0.32.0 10 Nov 2021 C1 — No Details →
0.31.0 12 Oct 2021 C1 — No Details →
0.30.1 29 Sep 2021 C1 — No Details →
0.30.0 16 Sep 2021 C1 — No Details →
0.29.1 10 Sep 2021 C1 — No Details →
0.29.0 02 Aug 2021 C1 — No Details →
0.28.0 13 Jul 2021 C1 — No Details →
0.27.0 15 Jun 2021 C1 — No Details →
0.26.2 19 May 2021 C1 — No Details →
0.26.1 18 May 2021 C1 — No Details →
0.26.0 11 May 2021 C1 — No Details →
0.25.4 05 May 2021 C1 — No Details →
0.25.3 29 Apr 2021 C1 — No Details →
0.25.2 21 Apr 2021 C1 — No Details →
0.25.1 15 Apr 2021 C1 — No Details →
0.25.0 02 Apr 2021 C1 — No Details →
0.24.1 24 Mar 2021 C1 — No Details →

The newest 120 of 211 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 2
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 4 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for qiskit

The 4 most severe of 4 vulnerabilities recorded for this package

Search all 4 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Arbitrary Code Execution Vulnerability in Qiskit Package 9.8 critical No fix published 14 Mar 2025
CVE-2025-2000: Qiskit Arbitrary Code Execution Vulnerability in QPY Format < 13 9.8 critical 2.0.0rc2 29 Jun 2026
CVE-2025-1403: Qiskit Denial of Service Vulnerability via Malicious QPY Files 8.6 high 1.3.0 21 Feb 2025
CVE-2025-1403: Qiskit Denial of Service Vulnerability via Malicious QPY Files 8.6 high 1.3.0 13 Jul 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About qiskit

Is qiskit safe to use?

Vulert records 4 vulnerabilities for qiskit in PyPI: 1 critical, 1 high, 0 medium and 0 low, plus 2 not yet rated. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is qiskit's Vulert package health score?

Vulert scores qiskit 60/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of qiskit affected?

Yes. 2.6.1, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

How many vulnerabilities does qiskit have?

4 vulnerabilities are recorded for qiskit in the PyPI ecosystem: 1 critical, 1 high, 0 medium and 0 low, plus 2 not yet rated. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new qiskit vulnerabilities disclosed?

2 vulnerabilities were recorded for qiskit in the last 12 months, and the oldest entry in this database dates to 21 Feb 2025. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of qiskit are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor qiskit for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the qiskit version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.