VulertSecurity VulertSecurity

Vulnerability Database · Bitnami · Package report

jupyterlab: vulnerability history, versions and safety

jupyterlab is a package in the Bitnami ecosystem. Vulert records 16 vulnerabilities for it across 14 affected ranges, from Mar 2024 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
16 vulnerabilities recorded C2 H6 M7 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
10 in the last 12 months

Most recent disclosure 14 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 i

Updated on 23 Oct 2026

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

Long-term outlook: usable, with an upgrade 16 vulnerabilities on record across 2 years, 10 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 16 over 2 years · 10 in the last year i
  • Latest disclosure 14 Oct 2026 i
  • Highest CVSS n/a 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

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

i
Affected range Vulnerabilities
from 4.0.0 up to 4.5.11 (exclusive) 1
up to 4.5.10 (exclusive) 2
from 4.5.0 up to 4.5.10 (exclusive) 1
from 3.3.0 up to 4.5.10 (exclusive) 1
from 4.1.0 up to 4.5.10 (exclusive) 1
up to 4.5.9 (exclusive) 1
up to 4.5.7 (exclusive) 2
from 4.0.0 up to 4.5.7 (exclusive) 1
up to 4.4.8 (exclusive) 1
up to 4.3.0 (exclusive) 1
up to 4.2.5 (exclusive) 1
from 4.0.0 up to 4.2.4 (exclusive) 1
up to 3.6.7 (exclusive) 1
up to 1.2.21 (exclusive) 1

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 4
  • 2025 2
  • 2026 10

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

03 Vulnerabilities

Recorded vulnerabilities for jupyterlab

The 5 most severe of 16 vulnerabilities recorded for this package

Search all 16 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-73626: JupyterLab Authentication Bypass via PyPIExtensionManager N/A high 4.5.10 25 Sep 2026
Vulnerability in JupyterLab Package: BIT-jupyterlab-2024-22420 N/A medium 4.2.4 06 Mar 2024
Authorization and XSRFToken Exposure in JupyterLab N/A medium 3.6.7 06 Mar 2024
CVE-2024-43805: Vulnerability in jupyterlab N/A medium 4.2.5 30 Aug 2024
CVE-2026-73627: JupyterLab Plugin Manager Lock-Rule Enforcement Bypass Vulnerability N/A medium 4.5.10 25 Sep 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 16 vulnerabilities for jupyterlab in Bitnami: 2 critical, 6 high, 7 medium and 1 low. 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 jupyterlab have?

16 vulnerabilities are recorded for jupyterlab in the Bitnami ecosystem: 2 critical, 6 high, 7 medium and 1 low. 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?

10 vulnerabilities were recorded for jupyterlab in the last 12 months, and the oldest entry in this database dates to 06 Mar 2024. 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.