VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

nbconvert: vulnerability history, versions and safety

nbconvert is a package in the PyPI ecosystem. Vulert records 9 vulnerabilities for it across 104 releases, from Aug 2022 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
9 vulnerabilities recorded H2 M3 U4
i
1 with no fix published

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

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

Most recent disclosure 22 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all nbconvert vulnerabilities

Vulert verdict on nbconvert 7.17.2 i

Updated on 23 Oct 2026

Careful: 7.17.2 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 Widely used
  • 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 7.17.2 — affected i
  • Vulnerabilities on record 9 over 4 years · 7 in the last year i
  • Latest disclosure 22 Oct 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 1 i
  • Depended on by 6,147 packages i
  • Stars 1,942 i
  • OpenSSF scorecard 4/10 i
  • Last release this month i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 22 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 nbconvert, 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
7.17.2 12 Oct 2026 H1 non-standard No Details →
7.17.1 08 Apr 2026 H1 non-standard Yes Details →
7.17.0 29 Jan 2026 H1 M2 U2 non-standard Yes Details →
7.16.6 28 Jan 2025 H2 M2 U3 non-standard No Details →
7.16.5 02 Jan 2025 H2 M2 U3 non-standard No Details →
7.16.4 29 Apr 2024 H2 M2 U3 non-standard No Details →
7.16.3 21 Mar 2024 H2 M2 U3 non-standard No Details →
7.16.2 04 Mar 2024 H2 M2 U3 non-standard No Details →
7.16.1 19 Feb 2024 H2 M2 U3 non-standard No Details →
7.16.0 07 Feb 2024 H2 M2 U3 non-standard No Details →
7.15.0 06 Feb 2024 H2 M2 U3 non-standard No Details →
7.14.2 16 Jan 2024 H2 M2 U3 non-standard No Details →
7.14.1 11 Jan 2024 H2 M2 U3 non-standard No Details →
7.14.0 01 Jan 2024 H2 M2 U3 non-standard No Details →
7.13.1 21 Dec 2023 H2 M2 U3 non-standard No Details →
7.13.0 18 Dec 2023 H2 M2 U3 non-standard No Details →
7.12.0 04 Dec 2023 H2 M2 U3 non-standard No Details →
7.11.0 06 Nov 2023 H2 M2 U3 non-standard No Details →
7.10.0 30 Oct 2023 H2 M2 U3 non-standard No Details →
7.9.2 05 Oct 2023 H2 M2 U3 non-standard No Details →
7.9.1 04 Oct 2023 H2 M2 U3 non-standard No Details →
7.9.0 04 Oct 2023 H2 M2 U3 non-standard No Details →
7.8.0 29 Aug 2023 H2 M2 U3 non-standard No Details →
7.7.4 16 Aug 2023 H2 M2 U3 non-standard No Details →
7.7.3 25 Jul 2023 H2 M2 U3 non-standard No Details →
7.7.2 19 Jul 2023 H2 M2 U3 non-standard No Details →
7.7.1 17 Jul 2023 H2 M2 U3 non-standard No Details →
7.7.0 17 Jul 2023 H2 M2 U3 non-standard No Details →
7.6.0 19 Jun 2023 H2 M2 U3 non-standard No Details →
7.5.0 13 Jun 2023 H2 M2 U3 non-standard No Details →
7.4.0 08 May 2023 H2 M2 U3 non-standard No Details →
7.3.1 10 Apr 2023 H2 M2 U3 non-standard No Details →
7.3.0 03 Apr 2023 H2 M2 U3 non-standard No Details →
7.2.10 14 Mar 2023 H2 M2 U3 non-standard No Details →
7.2.9 24 Jan 2023 H2 M2 U3 non-standard No Details →
7.2.8 16 Jan 2023 H2 M2 U3 non-standard No Details →
7.2.7 19 Dec 2022 H2 M2 U3 non-standard No Details →
7.2.6 05 Dec 2022 H2 M2 U3 non-standard No Details →
7.2.5 14 Nov 2022 H2 M2 U3 non-standard No Details →
7.2.4 09 Nov 2022 H2 M2 U3 non-standard No Details →
7.2.3 27 Oct 2022 H2 M2 U3 non-standard No Details →
7.2.2 19 Oct 2022 H2 M2 U3 non-standard No Details →
7.2.1 06 Oct 2022 H2 M2 U3 non-standard No Details →
7.2.0 06 Oct 2022 H2 M2 U3 non-standard No Details →
7.1.0 03 Oct 2022 H2 M2 U3 non-standard No Details →
6.5.4 26 Sep 2022 H2 M2 U3 non-standard No Details →
7.0.0 22 Aug 2022 H2 M2 U3 non-standard No Details →
6.5.3 11 Aug 2022 H2 M2 U3 non-standard No Details →
6.5.2 10 Aug 2022 H2 M2 U3 non-standard No Details →
6.5.1 09 Aug 2022 H2 M2 U3 non-standard No Details →
7.0.0rc3 14 Jul 2022 H2 M2 U3 non-standard No Details →
7.0.0rc2 15 Jun 2022 H2 M2 U3 non-standard No Details →
7.0.0rc1 16 May 2022 H2 M2 U3 non-standard No Details →
7.0.0rc0 09 May 2022 H2 M2 U3 non-standard No Details →
6.5.0 11 Apr 2022 H2 M3 U3 non-standard No Details →
6.4.5 28 Mar 2022 H2 M1 U1 non-standard No Details →
6.4.4 11 Mar 2022 H2 M1 U1 non-standard No Details →
6.4.3 11 Mar 2022 H2 M1 U1 non-standard No Details →
6.4.2 09 Feb 2022 H2 M1 U1 non-standard No Details →
6.4.1 26 Jan 2022 H2 M1 U1 non-standard No Details →
6.4.0 03 Jan 2022 H2 M1 U1 non-standard No Details →
6.3.0 12 Nov 2021 H2 M1 U1 non-standard No Details →
6.3.0b0 07 Nov 2021 H2 M1 U1 non-standard No Details →
6.2.0 25 Sep 2021 H2 M1 U2 non-standard No Details →
6.2.0rc2 17 Sep 2021 H2 M1 U2 non-standard No Details →
6.2.0rc1 15 Sep 2021 H2 M1 U2 non-standard No Details →
6.2.0rc0 14 Sep 2021 H2 M1 U2 non-standard No Details →
6.1.1b0 11 Sep 2021 H2 M1 U2 non-standard No Details →
6.1.0 22 Jun 2021 H2 M1 U2 non-standard No Details →
6.1.0rc0 08 Jun 2021 H2 M1 U2 non-standard No Details →
6.0.7 02 Oct 2020 H2 M1 U2 non-standard No Details →
6.0.6 23 Sep 2020 H2 M1 U2 non-standard No Details →
6.0.5 21 Sep 2020 H2 M1 U2 non-standard No Details →
6.0.4 20 Sep 2020 H2 M1 U2 non-standard No Details →
6.0.3 16 Sep 2020 H2 M1 U2 non-standard No Details →
6.0.2 13 Sep 2020 H2 M1 U2 non-standard No Details →
6.0.1 10 Sep 2020 H2 M1 U2 non-standard No Details →
6.0.0 10 Sep 2020 H2 M1 U2 non-standard No Details →
6.0.0rc0 07 Sep 2020 H2 M1 U2 non-standard No Details →
6.0.0b7 24 Aug 2020 H2 M1 U2 non-standard No Details →
6.0.0a6 18 Aug 2020 H2 M1 U2 non-standard No Details →
6.0.0a5 29 Jul 2020 H2 M1 U2 non-standard No Details →
6.0.0a4 07 Jul 2020 H2 M1 U2 non-standard No Details →
6.0.0a3 27 May 2020 H2 M1 U2 non-standard No Details →
6.0.0a2 26 May 2020 H2 M1 U2 non-standard No Details →
6.0.0a1 03 Apr 2020 H2 M1 U2 non-standard No Details →
6.0.0a0 24 Nov 2019 H2 M1 U2 non-standard No Details →
5.6.1 25 Oct 2019 H2 M1 U2 non-standard No Details →
5.6.0 09 Aug 2019 H2 M1 U2 non-standard No Details →
5.5.0 25 Apr 2019 H2 M1 U2 non-standard No Details →
5.4.1 09 Feb 2019 H2 M1 U2 non-standard No Details →
5.4.1.dev0 08 Feb 2019 H2 M1 U2 non-standard No Details →
5.4.0 06 Sep 2018 H2 M1 U2 non-standard No Details →
5.3.1 05 Sep 2017 H1 M1 U2 non-standard No Details →
5.3.0 31 Aug 2017 H1 M1 U2 non-standard No Details →
5.2.1 24 May 2017 H1 M1 U2 non-standard No Details →
5.1.1 21 Jan 2017 H1 M1 U2 non-standard No Details →
5.1.0 21 Jan 2017 H1 M1 U2 non-standard No Details →
5.0.0 15 Dec 2016 H1 M1 U2 non-standard No Details →
4.3.0 14 Dec 2016 H1 M1 U2 non-standard No Details →
5.0.0b1 20 Oct 2016 H1 M1 U2 — No Details →
4.2.0 08 Apr 2016 H1 M1 U2 — No Details →
4.1.0 30 Oct 2015 H1 M1 U2 — No Details →
4.0.0 12 Jul 2015 H1 M1 U2 — No Details →

All 104 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 2
  • 2025 1
  • 2026 6

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

03 Vulnerabilities

Recorded vulnerabilities for nbconvert

The 5 most severe of 9 vulnerabilities recorded for this package

Search all 9 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-114140: Arbitrary file write through path traversal in nbconvert 8.8 high 7.17.2 22 Oct 2026
CVE-2025-53000: nbconvert Uncontrolled Search Path Leading to Unauthorized Code Execution on Windows 8.5 high No fix published 18 Dec 2025
CVE-2025-53000: nbconvert Uncontrolled Search Path Leading to Unauthorized Code Execution on Windows 8.5 high 7.17.0 07 Jul 2026
CVE-2026-39377: nbconvert Arbitrary File Write via Path Traversal in Cell Attachment Filenames 6.5 medium 7.17.1 21 Apr 2026
CVE-2026-39378: nbconvert Arbitrary File Read via Path Traversal in HTMLExporter Image Embedding 6.5 medium 7.17.1 21 Apr 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 nbconvert

Is nbconvert safe to use?

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

What is nbconvert's Vulert package health score?

Vulert scores nbconvert 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 nbconvert affected?

Yes. 7.17.2, 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.

Which version of nbconvert should I use?

7.17.2 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 nbconvert have?

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

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

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