VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

ipython: vulnerability history, versions and safety

ipython is a package in the Debian ecosystem. Vulert records 12 vulnerabilities for it across 1 release, from Aug 2014 to Jan 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
12 vulnerabilities recorded U12
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.

See all ipython vulnerabilities

Vulert verdict on ipython i

Updated on 23 Oct 2026

Every vulnerability Vulert records for this package has a fix, and the newest was recorded 19 Jan 2022. Apply the fixes listed below and you are clear.

Long-term outlook: usable, with an upgrade 12 vulnerabilities on record across 7 years, none in the last year.

What to do: Move the affected dependencies to the fixed versions listed below, then keep the package monitored so the next vulnerability reaches you. Fix it, then keep watch: Vulert alerts you when a new vulnerability affects the version you run. Monitor it with Vulert →

  • Vulnerabilities on record 12 over 7 years · 0 in the last year i
  • Latest disclosure 19 Jan 2022 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i

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 holds for ipython, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
7.20.0-1 U2 Yes Details →

Newest 1 of 1 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2014 2
  • 2015 2
  • 2017 4
  • 2018 2
  • 2022 2

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

03 Vulnerabilities

Recorded vulnerabilities for ipython

The 5 most severe of 12 vulnerabilities recorded for this package

Search all 12 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Cross-Site Request Forgery Vulnerability in IPython: CVE-2015-5607 8.8 high 2.4.1-1 20 Sep 2017
Arbitrary Code Execution Vulnerability in IPython: A Cross-User Threat 8.8 high 7.20.0-1+deb11u1 19 Jan 2022
JavaScript Execution Vulnerability in Jupyter Notebook and IPython Packages 7.8 high 5.1.0-2 18 Mar 2018
Cross-Site Scripting (XSS) Vulnerability in IPython: Risk of Remote Code Injection 6.1 medium 2.4.1-1 20 Sep 2017
Remote Code Execution Vulnerability in IPython Notebook N/A unrated 1.2.0~rc1-1 07 Aug 2014

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 12 vulnerabilities for ipython in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 12 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.

How many vulnerabilities does ipython have?

12 vulnerabilities are recorded for ipython in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 12 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.