VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

jupyter-server: vulnerability history, versions and safety

jupyter-server is a package in the PyPI ecosystem. Vulert records 34 vulnerabilities for it across 120 releases, from Nov 2020 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
34 vulnerabilities recorded C1 H7 M9 U17
i
3 with no fix published

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

See the unfixed vulnerabilities →
i
17 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 jupyter-server vulnerabilities

Vulert verdict on jupyter-server 2.21.1 i

Updated on 23 Oct 2026

Careful: 2.21.1 has 9 known vulnerabilities, and 3 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 58/100
  • Security Unfixed issues
  • 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 2.21.1 — affected i
  • Vulnerabilities on record 34 over 5 years · 17 in the last year i
  • Latest disclosure 22 Oct 2026 i
  • Highest CVSS 9.3 i
  • With no published fix 3 i
  • Depended on by 5,044 packages i
  • Stars 572 i
  • Last release 1 month ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by PyPI, refreshed 23 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 jupyter-server, 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
2.21.1 15 Sep 2026 M1 U8 non-standard No Details →
2.21.0 27 Aug 2026 M1 U8 non-standard No Details →
2.20.0 17 Jun 2026 H1 U1 non-standard Yes Details →
2.19.0 29 May 2026 C1 H1 U2 non-standard Yes Details →
2.18.2 06 May 2026 C1 H1 U2 non-standard Yes Details →
2.18.1 05 May 2026 C1 H1 M1 U3 non-standard Yes Details →
2.18.0 04 May 2026 C1 H1 M1 U3 non-standard Yes Details →
2.17.0 21 Aug 2025 C1 H3 M4 U8 non-standard No Details →
2.16.0 12 May 2025 C1 H3 M4 U8 non-standard No Details →
2.15.0 20 Dec 2024 C1 H3 M4 U8 non-standard No Details →
2.14.2 12 Jul 2024 C1 H3 M4 U8 non-standard No Details →
2.14.1 31 May 2024 C1 H3 M4 U8 non-standard No Details →
2.14.0 11 Apr 2024 C1 H4 M4 U9 non-standard No Details →
2.13.0 04 Mar 2024 C1 H4 M4 U9 non-standard No Details →
2.12.5 16 Jan 2024 C1 H4 M4 U9 non-standard No Details →
2.12.4 11 Jan 2024 C1 H4 M4 U9 non-standard No Details →
2.12.3 09 Jan 2024 C1 H4 M4 U9 non-standard No Details →
2.12.2 04 Jan 2024 C1 H4 M4 U9 non-standard No Details →
2.12.1 06 Dec 2023 C1 H4 M4 U9 non-standard No Details →
2.12.0 05 Dec 2023 C1 H4 M4 U9 non-standard No Details →
2.11.2 04 Dec 2023 C1 H4 M4 U9 non-standard No Details →
2.11.1 27 Nov 2023 C1 H4 M5 U10 non-standard No Details →
2.11.0 21 Nov 2023 C1 H4 M5 U10 non-standard No Details →
2.10.1 15 Nov 2023 C1 H4 M5 U10 non-standard No Details →
2.10.0 06 Nov 2023 C1 H4 M5 U10 non-standard No Details →
2.9.1 25 Oct 2023 C1 H4 M5 U10 non-standard No Details →
2.9.0 25 Oct 2023 C1 H4 M5 U10 non-standard No Details →
2.8.0 16 Oct 2023 C1 H4 M5 U10 non-standard No Details →
2.7.3 31 Aug 2023 C1 H4 M5 U10 non-standard No Details →
2.7.2 18 Aug 2023 C1 H4 M5 U10 non-standard No Details →
2.7.1 15 Aug 2023 C1 H4 M7 U12 non-standard No Details →
2.7.0 27 Jun 2023 C1 H4 M7 U12 non-standard No Details →
2.6.0 25 May 2023 C1 H4 M7 U12 non-standard No Details →
1.24.0 13 Apr 2023 C1 H4 M7 U12 BSD-3-Clause No Details →
2.5.0 16 Mar 2023 C1 H5 M7 U12 non-standard No Details →
2.4.0 06 Mar 2023 C1 H5 M7 U12 non-standard No Details →
2.3.0 15 Feb 2023 C1 H5 M7 U12 non-standard No Details →
1.23.6 15 Feb 2023 C1 H4 M7 U12 BSD-3-Clause No Details →
2.2.1 02 Feb 2023 C1 H5 M7 U12 non-standard No Details →
2.2.0 31 Jan 2023 C1 H5 M7 U12 non-standard No Details →
2.1.0 13 Jan 2023 C1 H5 M7 U12 non-standard No Details →
1.23.5 12 Jan 2023 C1 H4 M7 U12 BSD-3-Clause No Details →
2.0.7 12 Jan 2023 C1 H5 M7 U12 non-standard No Details →
2.0.6 29 Dec 2022 C1 H5 M7 U12 non-standard No Details →
2.0.5 23 Dec 2022 C1 H5 M7 U12 non-standard No Details →
2.0.4 21 Dec 2022 C1 H5 M7 U12 non-standard No Details →
2.0.3 21 Dec 2022 C1 H5 M7 U12 non-standard No Details →
1.23.4 20 Dec 2022 C1 H4 M7 U12 BSD-3-Clause No Details →
2.0.2 20 Dec 2022 C1 H5 M7 U12 non-standard No Details →
2.0.1 08 Dec 2022 C1 H5 M7 U12 non-standard No Details →
2.0.0 06 Dec 2022 C1 H5 M7 U12 non-standard No Details →
2.0.0rc8 29 Nov 2022 C1 H4 M7 U12 non-standard No Details →
2.0.0rc7 23 Nov 2022 C1 H4 M7 U12 non-standard No Details →
2.0.0rc6 21 Nov 2022 C1 H4 M7 U12 non-standard No Details →
1.23.3 21 Nov 2022 C1 H4 M7 U12 BSD-3-Clause No Details →
2.0.0rc5 21 Nov 2022 C1 H4 M7 U12 non-standard No Details →
1.23.2 14 Nov 2022 C1 H4 M7 U12 BSD-3-Clause No Details →
2.0.0rc4 10 Nov 2022 C1 H4 M7 U12 non-standard No Details →
1.23.1 09 Nov 2022 C1 H4 M7 U12 BSD-3-Clause No Details →
1.23.0 07 Nov 2022 C1 H4 M7 U12 BSD-3-Clause No Details →
2.0.0rc3 17 Oct 2022 C1 H4 M7 U12 non-standard No Details →
1.21.0 11 Oct 2022 C1 H4 M7 U12 BSD-3-Clause No Details →
2.0.0rc2 11 Oct 2022 C1 H4 M7 U12 non-standard No Details →
2.0.0rc1 27 Sep 2022 C1 H4 M7 U12 non-standard No Details →
1.19.1 27 Sep 2022 C1 H4 M7 U12 BSD-3-Clause No Details →
1.19.0 26 Sep 2022 C1 H4 M7 U12 BSD-3-Clause No Details →
2.0.0rc0 13 Sep 2022 C1 H4 M7 U12 non-standard No Details →
2.0.0b1 01 Sep 2022 C1 H4 M7 U12 non-standard No Details →
2.0.0b0 14 Jul 2022 C1 H4 M7 U12 non-standard No Details →
2.0.0a2 05 Jul 2022 C1 H4 M7 U12 non-standard No Details →
1.18.1 05 Jul 2022 C1 H4 M7 U12 BSD-3-Clause No Details →
1.18.0 23 Jun 2022 C1 H4 M7 U12 BSD-3-Clause No Details →
1.17.1 07 Jun 2022 C1 H4 M7 U12 BSD-3-Clause No Details →
2.0.0a1 07 Jun 2022 C1 H4 M7 U12 non-standard No Details →
2.0.0a0 03 May 2022 C1 H4 M7 U12 non-standard No Details →
1.17.0 27 Apr 2022 C1 H5 M7 U12 BSD-3-Clause No Details →
1.16.0 29 Mar 2022 C1 H5 M7 U13 BSD-3-Clause No Details →
1.15.6 16 Mar 2022 C1 H5 M7 U13 BSD-3-Clause No Details →
1.15.5 16 Mar 2022 C1 H5 M7 U13 BSD-3-Clause No Details →
1.15.4 15 Mar 2022 C1 H5 M7 U13 BSD-3-Clause No Details →
1.15.3 14 Mar 2022 C1 H6 M7 U14 BSD-3-Clause No Details →
1.15.2 14 Mar 2022 C1 H6 M7 U14 BSD-3-Clause No Details →
1.15.1 14 Mar 2022 C1 H6 M7 U14 BSD-3-Clause No Details →
1.15.0 14 Mar 2022 C1 H6 M7 U14 BSD-3-Clause No Details →
1.13.5 05 Feb 2022 C1 H6 M7 U14 BSD-3-Clause No Details →
1.13.4 21 Jan 2022 C1 H6 M7 U14 BSD-3-Clause No Details →
1.13.3 14 Jan 2022 C1 H6 M7 U14 BSD-3-Clause No Details →
1.13.2 12 Jan 2022 C1 H6 M7 U14 BSD-3-Clause No Details →
1.13.1 09 Dec 2021 C1 H6 M7 U14 BSD-3-Clause No Details →
1.13.0 06 Dec 2021 C1 H6 M7 U14 BSD-3-Clause No Details →
1.12.1 26 Nov 2021 C1 H6 M7 U14 BSD-3-Clause No Details →
1.12.0 23 Nov 2021 C1 H6 M7 U14 BSD-3-Clause No Details →
1.11.2 01 Nov 2021 C1 H6 M6 U13 BSD-3-Clause Yes Details →
1.11.1 04 Oct 2021 C1 H6 M6 U13 BSD-3-Clause Yes Details →
1.11.0 09 Sep 2021 C1 H6 M6 U13 BSD-3-Clause Yes Details →
1.10.2 02 Aug 2021 C1 H6 M6 U13 BSD-3-Clause Yes Details →
1.10.1 23 Jul 2021 C1 H6 M6 U13 BSD-3-Clause Yes Details →
1.10.0 22 Jul 2021 C1 H6 M6 U13 BSD-3-Clause Yes Details →
1.9.0 24 Jun 2021 C1 H6 M6 U13 BSD-3-Clause Yes Details →
1.8.0 20 May 2021 C1 H6 M6 U13 non-standard Yes Details →
1.7.0 10 May 2021 C1 H6 M6 U13 — Yes Details →
1.7.0a2 06 May 2021 C1 H6 M6 U13 — Yes Details →
1.7.0a1 05 May 2021 C1 H6 M6 U13 — Yes Details →
1.6.4 21 Apr 2021 C1 H6 M6 U13 — Yes Details →
1.6.3 21 Apr 2021 C1 H6 M6 U13 — Yes Details →
1.6.2 16 Apr 2021 C1 H6 M6 U13 — Yes Details →
1.6.1 12 Apr 2021 C1 H6 M6 U13 — Yes Details →
1.6.0 08 Apr 2021 C1 H6 M6 U13 — Yes Details →
1.5.1 24 Mar 2021 C1 H6 M6 U13 — Yes Details →
1.5.0 23 Mar 2021 C1 H6 M6 U13 — Yes Details →
1.4.1 22 Feb 2021 C1 H6 M6 U13 — Yes Details →
1.4.0 18 Feb 2021 C1 H6 M6 U13 — Yes Details →
1.3.0 05 Feb 2021 C1 H6 M6 U13 — Yes Details →
1.2.3 29 Jan 2021 C1 H6 M6 U13 — Yes Details →
1.2.2 15 Jan 2021 C1 H6 M6 U13 — Yes Details →
1.2.1 08 Jan 2021 C1 H6 M6 U13 — Yes Details →
1.2.0 07 Jan 2021 C1 H6 M6 U13 — Yes Details →
1.1.4 04 Jan 2021 C1 H6 M6 U13 — Yes Details →
1.1.3 23 Dec 2020 C1 H6 M6 U13 — Yes Details →
1.1.2 21 Dec 2020 C1 H6 M6 U13 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 5
  • 2022 4
  • 2023 6
  • 2024 2
  • 2026 17

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

03 Vulnerabilities

Recorded vulnerabilities for jupyter-server

The 5 most severe of 34 vulnerabilities recorded for this package

Search all 34 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-44727: Jupyter Server Stored XSS Vulnerability via Nbconvert Handlers 9.3 critical 2.20.0 18 Jun 2026
CVE-2026-44727: jupyter-server Stored XSS via Missing Sandbox CSP 9.3 critical 2.20.0 29 Jun 2026
CVE-2026-114135: Jupyter Server gateway WebSocket handler skips kernel authorization 8.8 high 2.6.0 22 Oct 2026
CVE-2026-35397: Jupyter Server Path Traversal Vulnerability Allows Unauthorized Access to Sibling Directories 8.8 high 2.18.0 05 May 2026
CVE-2026-40110: Jupyter Server CORS Origin Validation Bypass Vulnerability 7.6 high 2.18.0 05 May 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 jupyter-server

Is jupyter-server safe to use?

Vulert records 34 vulnerabilities for jupyter-server in PyPI: 1 critical, 7 high, 9 medium and 0 low, plus 17 not yet rated. 3 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is jupyter-server's Vulert package health score?

Vulert scores jupyter-server 58/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 jupyter-server affected?

Yes. 2.21.1, the version you would install today, has 9 known vulnerabilities, and 3 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of jupyter-server should I use?

2.21.1 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 jupyter-server have?

34 vulnerabilities are recorded for jupyter-server in the PyPI ecosystem: 1 critical, 7 high, 9 medium and 0 low, plus 17 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?

17 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.