VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

jupyterlab: vulnerability history, versions and safety

jupyterlab is a package in the PyPI ecosystem. Vulert records 32 vulnerabilities for it across 120 releases, from Aug 2021 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
32 vulnerabilities recorded H7 M8 L2 U15
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
25 in the last 12 months

Most recent disclosure 15 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all jupyterlab vulnerabilities

Vulert verdict on jupyterlab 4.6.4 i

Updated on 23 Oct 2026

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

Package health score 68/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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 4.6.4 — affected i
  • Vulnerabilities on record 32 over 5 years · 25 in the last year i
  • Latest disclosure 15 Oct 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 3,939 packages i
  • Stars 15,363 i
  • OpenSSF scorecard 6/10 i
  • Last release 1 month ago 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 jupyterlab, 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
4.7.0a2 21 Sep 2026 U1 non-standard Yes Details →
4.5.11 21 Sep 2026 U1 non-standard Yes Details →
4.6.4 21 Sep 2026 U1 non-standard Yes Details →
4.6.3 10 Aug 2026 H1 M3 U3 non-standard Yes Details →
4.7.0a1 21 Jul 2026 U1 non-standard Yes Details →
4.5.10 21 Jul 2026 U3 non-standard Yes Details →
4.6.2 21 Jul 2026 H1 M3 U3 non-standard Yes Details →
4.6.1 29 Jun 2026 H3 M5 L1 U6 non-standard Yes Details →
4.7.0a0 29 Jun 2026 U1 non-standard Yes Details →
4.6.0 18 Jun 2026 H3 M5 L1 U6 non-standard Yes Details →
4.5.9 17 Jun 2026 U6 non-standard Yes Details →
4.6.0rc1 17 Jun 2026 U1 non-standard Yes Details →
4.6.0rc0 10 Jun 2026 U1 non-standard Yes Details →
4.5.8 04 Jun 2026 M1 U6 non-standard Yes Details →
4.6.0b1 28 May 2026 U1 non-standard Yes Details →
4.6.0b0 20 May 2026 U1 non-standard Yes Details →
4.5.7 29 Apr 2026 M1 U6 non-standard Yes Details →
4.6.0a5 29 Apr 2026 U1 non-standard Yes Details →
4.5.6 11 Mar 2026 H2 M1 U9 non-standard Yes Details →
4.6.0a4 11 Mar 2026 U1 non-standard Yes Details →
4.5.5 23 Feb 2026 H2 M1 U9 non-standard Yes Details →
4.6.0a3 23 Feb 2026 U1 non-standard Yes Details →
4.5.4 11 Feb 2026 H2 M1 U9 non-standard Yes Details →
4.5.3 23 Jan 2026 H2 M1 U9 non-standard Yes Details →
4.6.0a2 22 Jan 2026 U1 non-standard Yes Details →
4.6.0a1 12 Jan 2026 U1 non-standard Yes Details →
4.5.2 12 Jan 2026 H2 M1 U9 non-standard Yes Details →
4.6.0a0 15 Dec 2025 U1 non-standard Yes Details →
4.5.1 15 Dec 2025 H2 M1 U9 non-standard Yes Details →
4.5.0 18 Nov 2025 H2 M1 U9 non-standard Yes Details →
4.5.0rc1 13 Nov 2025 H2 M1 U7 non-standard Yes Details →
4.5.0rc0 30 Oct 2025 H2 M1 U7 non-standard Yes Details →
4.4.10 22 Oct 2025 H2 M1 U7 non-standard Yes Details →
4.5.0b1 16 Oct 2025 H2 M1 U7 non-standard Yes Details →
4.5.0b0 27 Sep 2025 H2 M1 U7 non-standard Yes Details →
4.4.9 26 Sep 2025 H2 M1 U7 non-standard Yes Details →
4.4.8 25 Sep 2025 H2 M1 U7 non-standard Yes Details →
4.5.0a4 22 Sep 2025 H2 M1 U7 non-standard Yes Details →
4.4.7 03 Sep 2025 H2 M1 L1 U8 non-standard Yes Details →
4.5.0a3 15 Aug 2025 H2 M1 U7 non-standard Yes Details →
4.4.6 15 Aug 2025 H2 M1 L1 U8 non-standard Yes Details →
4.5.0a2 08 Aug 2025 H2 M1 U7 non-standard Yes Details →
4.4.5 20 Jul 2025 H2 M1 L1 U8 non-standard Yes Details →
4.4.4 28 Jun 2025 H2 M1 L1 U8 non-standard Yes Details →
4.3.8 24 Jun 2025 H2 M1 L1 U8 non-standard Yes Details →
4.5.0a1 26 May 2025 H2 M1 U7 non-standard Yes Details →
4.4.3 26 May 2025 H2 M1 L1 U8 non-standard Yes Details →
4.5.0a0 07 May 2025 H2 M1 U7 non-standard Yes Details →
4.4.2 06 May 2025 H2 M1 L1 U8 non-standard Yes Details →
4.3.7 30 Apr 2025 H2 M1 L1 U8 non-standard Yes Details →
4.4.1 22 Apr 2025 H2 M1 L1 U8 non-standard Yes Details →
4.4.0 03 Apr 2025 H2 M1 L1 U8 non-standard Yes Details →
4.4.0rc1 02 Apr 2025 H2 M1 L1 U8 non-standard Yes Details →
4.4.0rc0 25 Mar 2025 H2 M1 L1 U8 non-standard Yes Details →
4.4.0b2 19 Mar 2025 H2 M1 L1 U8 non-standard Yes Details →
4.3.6 14 Mar 2025 H2 M1 L1 U8 non-standard Yes Details →
4.4.0b1 13 Mar 2025 H2 M1 L1 U8 non-standard Yes Details →
4.4.0b0 19 Feb 2025 H2 M1 L1 U8 non-standard Yes Details →
4.3.5 29 Jan 2025 H2 M1 L1 U8 non-standard Yes Details →
4.4.0a3 28 Jan 2025 H2 M1 L1 U8 non-standard Yes Details →
4.2.7 08 Jan 2025 H2 M1 L1 U9 non-standard Yes Details →
4.4.0a2 06 Jan 2025 H2 M1 L1 U8 non-standard Yes Details →
4.4.0a1 18 Dec 2024 H2 M1 L1 U8 non-standard Yes Details →
4.3.4 18 Dec 2024 H2 M1 L1 U8 non-standard Yes Details →
4.3.3 10 Dec 2024 H2 M1 L1 U8 non-standard Yes Details →
4.3.2 03 Dec 2024 H2 M1 L1 U8 non-standard Yes Details →
4.4.0a0 19 Nov 2024 H2 M1 L1 U8 non-standard Yes Details →
4.3.1 16 Nov 2024 H2 M1 L1 U8 non-standard Yes Details →
4.2.6 15 Nov 2024 H2 M1 L1 U9 non-standard Yes Details →
4.3.0 30 Oct 2024 H2 M1 L1 U8 non-standard Yes Details →
4.3.0rc1 24 Oct 2024 H2 M1 L1 U9 non-standard Yes Details →
4.3.0rc0 14 Oct 2024 H2 M1 L1 U9 non-standard Yes Details →
4.3.0b3 07 Oct 2024 H2 M1 L1 U9 non-standard Yes Details →
4.3.0b2 27 Sep 2024 H2 M1 L1 U9 non-standard Yes Details →
3.6.8 26 Aug 2024 H1 M1 L1 U7 BSD-3-Clause Yes Details →
4.2.5 26 Aug 2024 H2 M1 L1 U9 non-standard Yes Details →
4.3.0b1 26 Aug 2024 H2 M1 L1 U9 non-standard Yes Details →
4.3.0b0 11 Aug 2024 H2 M1 L1 U9 non-standard Yes Details →
4.2.4 18 Jul 2024 H2 M1 L1 U10 non-standard Yes Details →
4.3.0a2 11 Jul 2024 H2 M1 L1 U9 non-standard Yes Details →
4.3.0a1 28 Jun 2024 H2 M1 L1 U9 non-standard Yes Details →
4.2.3 26 Jun 2024 H2 M1 L1 U10 non-standard Yes Details →
4.2.2 10 Jun 2024 H2 M1 L1 U10 non-standard Yes Details →
4.3.0a0 23 May 2024 H2 M1 L1 U9 non-standard Yes Details →
4.2.1 23 May 2024 H2 M1 L1 U10 non-standard Yes Details →
4.2.0 06 May 2024 H2 M1 L1 U10 non-standard Yes Details →
4.2.0rc0 26 Apr 2024 H2 M1 L1 U10 non-standard Yes Details →
4.1.8 26 Apr 2024 H2 M1 L1 U10 non-standard Yes Details →
4.1.7 26 Apr 2024 H2 M1 L1 U10 non-standard Yes Details →
4.2.0b3 19 Apr 2024 H2 M1 L1 U10 non-standard Yes Details →
4.2.0b2 18 Apr 2024 H2 M1 L1 U10 non-standard Yes Details →
4.2.0b1 09 Apr 2024 H2 M1 L1 U10 non-standard Yes Details →
4.1.6 08 Apr 2024 H2 M1 L1 U10 non-standard Yes Details →
4.2.0b0 02 Apr 2024 H2 M1 L1 U10 non-standard Yes Details →
4.2.0a2 25 Mar 2024 H2 M1 L1 U10 non-standard Yes Details →
4.2.0a1 14 Mar 2024 H2 M1 L1 U10 non-standard Yes Details →
4.1.5 14 Mar 2024 H2 M1 L1 U10 non-standard Yes Details →
4.1.4 07 Mar 2024 H2 M1 L1 U10 non-standard Yes Details →
4.2.0a0 05 Mar 2024 H2 M1 L1 U10 non-standard Yes Details →
4.1.3 04 Mar 2024 H2 M1 L1 U10 non-standard Yes Details →
4.0.13 26 Feb 2024 H2 M1 L1 U10 — Yes Details →
4.1.2 19 Feb 2024 H2 M1 L1 U10 — Yes Details →
4.1.1 13 Feb 2024 H2 M1 L1 U10 — Yes Details →
4.1.0 05 Feb 2024 H2 M1 L1 U10 — Yes Details →
4.1.0rc1 01 Feb 2024 H2 M1 L1 U10 — Yes Details →
4.0.12 30 Jan 2024 H2 M1 L1 U10 — Yes Details →
4.1.0rc0 27 Jan 2024 H2 M1 L1 U10 — Yes Details →
4.1.0b2 19 Jan 2024 H2 M1 L1 U10 — Yes Details →
3.6.7 19 Jan 2024 H2 M1 L1 U8 — Yes Details →
4.0.11 19 Jan 2024 H2 M1 L1 U10 — Yes Details →
4.1.0b1 17 Jan 2024 H2 M1 L1 U10 — Yes Details →
4.0.10 29 Dec 2023 H3 M2 L1 U12 — Yes Details →
4.1.0b0 20 Dec 2023 H2 M1 L1 U10 — Yes Details →
4.1.0a4 30 Nov 2023 H2 M1 L1 U10 — Yes Details →
4.0.9 18 Nov 2023 H3 M2 L1 U12 — Yes Details →
4.1.0a3 12 Nov 2023 H2 M1 L1 U10 — Yes Details →
4.0.8 02 Nov 2023 H3 M2 L1 U12 — Yes Details →
4.0.7 11 Oct 2023 H3 M2 L1 U12 — Yes Details →
4.1.0a2 03 Oct 2023 H2 M1 L1 U10 — Yes Details →
3.6.6 26 Sep 2023 H2 M1 L1 U9 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 2
  • 2024 4
  • 2025 1
  • 2026 25

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

03 Vulnerabilities

Recorded vulnerabilities for jupyterlab

The 5 most severe of 32 vulnerabilities recorded for this package

Search all 32 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-39700: JupyterLab RCE Vulnerability in Extension Template 9.8 critical 4.3.0 16 Jul 2024
CVE-2026-42557: JupyterLab Command Linker Vulnerability Allows Arbitrary Command Execution from Untrusted Content 9.6 critical 4.5.7 13 Jul 2026
CVE-2026-42266: JupyterLab Extension Manager API Policy Discrepancy Leading to Malicious Extension Installation 8.8 high 4.5.7 05 May 2026
CVE-2026-42266: JupyterLab Extension Manager Bypass Vulnerability 8.8 high 4.5.7 13 May 2026
Cross-Site Scripting (XSS) Vulnerability in JupyterLab: Exploitable via Overrides.json 8.6 high 4.6.2 22 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 jupyterlab

Is jupyterlab safe to use?

Vulert records 32 vulnerabilities for jupyterlab in PyPI: 0 critical, 7 high, 8 medium and 2 low, plus 15 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 jupyterlab's Vulert package health score?

Vulert scores jupyterlab 68/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).

Is the latest version of jupyterlab affected?

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

Which version of jupyterlab should I use?

4.6.4 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 jupyterlab have?

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

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

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