VulertSecurity VulertSecurity

Vulnerability Database · Debian · Package report

jupyter-server: vulnerability history, versions and safety

jupyter-server is a package in the Debian ecosystem. Vulert records 16 vulnerabilities for it across 26 releases, from Nov 2020 to Jun 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 U16
i
12 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 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all jupyter-server vulnerabilities

Vulert verdict on jupyter-server i

Updated on 23 Oct 2026

Careful: 12 of the 16 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 16 vulnerabilities on record across 5 years, 7 in the last year.

What to do: Plan around the 12 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 16 over 5 years · 7 in the last year i
  • Latest disclosure 22 Jun 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 12 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 jupyter-server, 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.

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 4
  • 2022 2
  • 2023 3
  • 2026 7

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

03 Vulnerabilities

Recorded vulnerabilities for jupyter-server

The 5 most severe of 16 vulnerabilities recorded for this package

Search all 16 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Access Token Leakage in Jupyter Server: CVE-2022-29241 8.8 high No fix published 14 Jun 2022
Path Traversal Vulnerability in jupyter-server: Unauthorized Access Risk 8.1 high No fix published 02 Jun 2026
Sensitive Information Exposure in Jupyter Server - CVE-2022-24757 7.5 high No fix published 23 Mar 2022
Open Redirect Vulnerability in Jupyter Server - CVE-2020-26275 6.1 medium 1.1.1-1 21 Dec 2020
Open Redirect Vulnerability in jupyter-server: Risk of Arbitrary Redirection 6.1 medium No fix published 28 Aug 2023

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 jupyter-server

Is jupyter-server safe to use?

Vulert records 16 vulnerabilities for jupyter-server in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 16 not yet rated. 12 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does jupyter-server have?

16 vulnerabilities are recorded for jupyter-server in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 16 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 jupyter-server vulnerabilities disclosed?

7 vulnerabilities were recorded for jupyter-server in the last 12 months, and the oldest entry in this database dates to 24 Nov 2020. 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 jupyter-server 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 jupyter-server for upcoming vulnerabilities?

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