Vulnerability Database · PyPI · Package report

ipython: vulnerability history, versions and safety

ipython is a package in the PyPI ecosystem. Vulert records 14 vulnerabilities for it across 120 releases, from Aug 2014 to Feb 2023. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
14 vulnerabilities recorded H3 M2 L1 U8
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on ipython 9.17.1 i

Updated on 23 Oct 2026

Action needed: 9.17.1 has 2 known vulnerabilities, but every one of them has a fix. Upgrade to the version listed below and you are clear.

Package health score 87/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Active

What to do: Upgrade to the version that resolves each vulnerability below. Fix it, then keep watch: this version is affected today, and the next one may be too — Vulert alerts you when a new vulnerability lands. Monitor it with Vulert →

  • Current release 9.17.1 — affected i
  • Vulnerabilities on record 14 over 8 years · 0 in the last year i
  • Latest disclosure 10 Feb 2023 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 15,371 packages i
  • Stars 16,792 i
  • OpenSSF scorecard 7/10 i
  • Last release 1 month ago i
  • Licence BSD-3-Clause 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 ipython, 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
9.17.1 01 Sep 2026 U2 BSD-3-Clause Yes Details →
9.17.0 28 Aug 2026 U2 BSD-3-Clause Yes Details →
9.16.1 03 Aug 2026 U2 BSD-3-Clause Yes Details →
9.16.0 31 Jul 2026 U2 BSD-3-Clause Yes Details →
9.15.0 26 Jun 2026 U2 BSD-3-Clause Yes Details →
9.14.1 05 Jun 2026 U2 BSD-3-Clause Yes Details →
9.14.0 29 May 2026 U2 BSD-3-Clause Yes Details →
9.13.0 24 Apr 2026 U2 BSD-3-Clause Yes Details →
8.39.0 27 Mar 2026 U2 BSD-3-Clause Yes Details →
9.10.1 27 Mar 2026 U2 BSD-3-Clause Yes Details →
9.12.0 27 Mar 2026 U2 BSD-3-Clause Yes Details →
9.11.0 05 Mar 2026 U2 BSD-3-Clause Yes Details →
9.10.0 02 Feb 2026 U2 BSD-3-Clause Yes Details →
9.9.0 05 Jan 2026 U2 BSD-3-Clause Yes Details →
8.38.0 05 Jan 2026 U2 BSD-3-Clause Yes Details →
9.8.0 03 Dec 2025 U2 BSD-3-Clause Yes Details →
9.7.0 05 Nov 2025 U2 BSD-3-Clause Yes Details →
9.6.0 29 Sep 2025 U2 BSD-3-Clause Yes Details →
9.5.0 29 Aug 2025 U2 BSD-3-Clause Yes Details →
9.4.0 01 Jul 2025 U2 BSD-3-Clause Yes Details →
8.37.0 31 May 2025 U2 BSD-3-Clause Yes Details →
9.3.0 31 May 2025 U2 BSD-3-Clause Yes Details →
8.36.0 25 Apr 2025 U2 BSD-3-Clause Yes Details →
9.2.0 25 Apr 2025 U2 BSD-3-Clause Yes Details →
8.35.0 07 Apr 2025 U2 BSD-3-Clause Yes Details →
9.1.0 07 Apr 2025 U2 BSD-3-Clause Yes Details →
9.0.2 08 Mar 2025 U2 BSD-3-Clause Yes Details →
8.34.0 08 Mar 2025 U2 BSD-3-Clause Yes Details →
9.0.1 03 Mar 2025 U2 BSD-3-Clause Yes Details →
8.33.0 28 Feb 2025 U2 BSD-3-Clause Yes Details →
9.0.0 28 Feb 2025 U2 BSD-3-Clause Yes Details →
9.0.0b2 26 Feb 2025 U2 BSD-3-Clause Yes Details →
9.0.0b1 24 Feb 2025 U2 BSD-3-Clause Yes Details →
8.32.0 31 Jan 2025 U2 BSD-3-Clause Yes Details →
8.31.0 20 Dec 2024 U2 BSD-3-Clause Yes Details →
8.30.0 29 Nov 2024 U2 BSD-3-Clause Yes Details →
8.29.0 25 Oct 2024 U2 BSD-3-Clause Yes Details →
8.28.0 02 Oct 2024 U2 BSD-3-Clause Yes Details →
8.27.0 30 Aug 2024 U2 BSD-3-Clause Yes Details →
8.26.0 28 Jun 2024 U2 BSD-3-Clause Yes Details →
8.25.0 31 May 2024 U2 BSD-3-Clause Yes Details →
8.24.0 26 Apr 2024 U2 BSD-3-Clause Yes Details →
8.23.0 31 Mar 2024 U2 BSD-3-Clause Yes Details →
8.22.2 04 Mar 2024 U2 BSD-3-Clause Yes Details →
8.22.1 22 Feb 2024 U2 BSD-3-Clause Yes Details →
8.22.0 22 Feb 2024 U2 BSD-3-Clause Yes Details →
8.21.0 31 Jan 2024 U2 BSD-3-Clause Yes Details →
8.20.0 08 Jan 2024 U2 BSD-3-Clause Yes Details →
8.19.0 22 Dec 2023 U2 BSD-3-Clause Yes Details →
8.18.1 27 Nov 2023 U2 BSD-3-Clause Yes Details →
8.18.0 24 Nov 2023 U2 BSD-3-Clause Yes Details →
8.17.2 31 Oct 2023 U2 BSD-3-Clause Yes Details →
8.17.1 30 Oct 2023 U2 BSD-3-Clause Yes Details →
8.17.0 30 Oct 2023 U2 BSD-3-Clause Yes Details →
8.16.1 02 Oct 2023 U2 BSD-3-Clause Yes Details →
8.16.0 29 Sep 2023 U2 BSD-3-Clause Yes Details →
8.12.3 29 Sep 2023 U2 BSD-3-Clause Yes Details →
8.15.0 01 Sep 2023 U2 BSD-3-Clause Yes Details →
8.14.0 02 Jun 2023 U2 BSD-3-Clause Yes Details →
8.13.2 04 May 2023 U2 BSD-3-Clause Yes Details →
8.12.2 04 May 2023 U2 BSD-3-Clause Yes Details →
8.13.1 29 Apr 2023 U2 BSD-3-Clause Yes Details →
8.13.0 28 Apr 2023 U2 BSD-3-Clause Yes Details →
8.12.1 28 Apr 2023 U2 BSD-3-Clause Yes Details →
8.12.0 30 Mar 2023 U2 BSD-3-Clause Yes Details →
8.11.0 28 Feb 2023 U2 BSD-3-Clause Yes Details →
8.10.0 10 Feb 2023 U2 BSD-3-Clause Yes Details →
8.9.0 27 Jan 2023 L1 U1 BSD-3-Clause Yes Details →
8.8.0 03 Jan 2023 L1 U1 BSD-3-Clause Yes Details →
8.7.0 28 Nov 2022 L1 U1 BSD-3-Clause Yes Details →
8.6.0 30 Oct 2022 L1 U1 BSD-3-Clause Yes Details →
8.5.0 06 Sep 2022 L1 U1 non-standard Yes Details →
8.4.0 28 May 2022 L1 U1 non-standard Yes Details →
7.34.0 28 May 2022 L1 U1 non-standard Yes Details →
8.3.0 29 Apr 2022 L1 U1 non-standard Yes Details →
7.33.0 29 Apr 2022 L1 U1 non-standard Yes Details →
8.2.0 27 Mar 2022 L1 U1 non-standard Yes Details →
8.1.1 03 Mar 2022 L1 U1 non-standard Yes Details →
8.1.0 25 Feb 2022 L1 U1 non-standard Yes Details →
7.32.0 25 Feb 2022 L1 U1 non-standard Yes Details →
7.16.3 19 Jan 2022 L1 U1 non-standard Yes Details →
7.31.1 19 Jan 2022 L1 U1 non-standard Yes Details →
8.0.1 19 Jan 2022 L1 U1 non-standard Yes Details →
8.0.0 12 Jan 2022 L1 U2 non-standard Yes Details →
8.0.0rc1 05 Jan 2022 L1 U1 non-standard Yes Details →
7.31.0 05 Jan 2022 L1 U2 non-standard Yes Details →
8.0.0b1 26 Dec 2021 L1 U1 non-standard Yes Details →
8.0.0a1 11 Dec 2021 L1 U1 non-standard Yes Details →
7.30.1 02 Dec 2021 L1 U2 non-standard Yes Details →
7.30.0 26 Nov 2021 L1 U2 non-standard Yes Details →
7.16.2 26 Nov 2021 L1 U2 non-standard Yes Details →
7.29.0 30 Oct 2021 L1 U2 non-standard Yes Details →
7.28.0 25 Sep 2021 L1 U2 non-standard Yes Details →
7.27.0 27 Aug 2021 L1 U2 non-standard Yes Details →
7.26.0 01 Aug 2021 L1 U2 non-standard Yes Details →
7.25.0 25 Jun 2021 L1 U2 non-standard Yes Details →
7.24.1 02 Jun 2021 L1 U2 non-standard Yes Details →
7.24.0 28 May 2021 L1 U2 non-standard Yes Details →
7.23.1 05 May 2021 L1 U2 non-standard Yes Details →
7.23.0 30 Apr 2021 L1 U2 non-standard Yes Details →
7.22.0 27 Mar 2021 L1 U2 — Yes Details →
7.21.0 26 Feb 2021 L1 U2 — Yes Details →
7.20.0 01 Feb 2021 L1 U2 — Yes Details →
7.19.0 30 Oct 2020 L1 U2 — Yes Details →
7.18.1 29 Aug 2020 L1 U2 — Yes Details →
7.18.0 28 Aug 2020 L1 U2 — Yes Details →
7.17.0 01 Aug 2020 L1 U2 — Yes Details →
7.16.1 26 Jun 2020 L1 U2 — Yes Details →
7.16.0 26 Jun 2020 L1 U2 — Yes Details →
7.15.0 29 May 2020 L1 U2 — Yes Details →
7.14.0 01 May 2020 L1 U2 — Yes Details →
5.10.0 01 May 2020 H1 L1 U2 — Yes Details →
7.13.0 29 Feb 2020 L1 U2 — Yes Details →
5.9.0 01 Feb 2020 H1 L1 U2 — Yes Details →
7.12.0 01 Feb 2020 L1 U2 — Yes Details →
7.11.1 01 Jan 2020 L1 U2 — Yes Details →
7.11.0 27 Dec 2019 L1 U2 — Yes Details →
7.10.2 14 Dec 2019 L1 U2 — Yes Details →
7.10.1 01 Dec 2019 L1 U2 — Yes Details →
7.10.0 27 Nov 2019 L1 U2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 1
  • 2015 2
  • 2017 3
  • 2022 6
  • 2023 2

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

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 ipython

Is ipython safe to use?

Vulert records 14 vulnerabilities for ipython in PyPI: 0 critical, 3 high, 2 medium and 1 low, plus 8 not yet rated. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is ipython's Vulert package health score?

Vulert scores ipython 87/100, which reads as healthy. 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).

Is the latest version of ipython affected?

Yes. 9.17.1, the version you would install today, has 2 known vulnerabilities, and every one of them has a published fix. Upgrade to the version listed for each.

Which version of ipython should I use?

9.17.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does ipython have?

14 vulnerabilities are recorded for ipython in the PyPI ecosystem: 0 critical, 3 high, 2 medium and 1 low, plus 8 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 ipython vulnerabilities disclosed?

0 vulnerabilities were recorded for ipython in the last 12 months, and the oldest entry in this database dates to 07 Aug 2014. 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 ipython 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 ipython for upcoming vulnerabilities?

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