VulertSecurity VulertSecurity

Vulnerability Database · PyPI · Package report

jupyterhub: vulnerability history, versions and safety

jupyterhub is a package in the PyPI ecosystem. Vulert records 17 vulnerabilities for it across 108 releases, from Feb 2018 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
17 vulnerabilities recorded H2 M6 U9
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
8 in the last 12 months

Most recent disclosure 10 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all jupyterhub vulnerabilities

Vulert verdict on jupyterhub 6.1.1 i

Updated on 23 Oct 2026

Action needed: 6.1.1 has 2 known vulnerabilities, 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 Widely used
  • 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 6.1.1 — affected i
  • Vulnerabilities on record 17 over 8 years · 8 in the last year i
  • Latest disclosure 10 Sep 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Depended on by 154 packages i
  • Stars 8,358 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence BSD-3-Clause 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 jupyterhub, 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
6.1.1 20 Oct 2026 U2 BSD-3-Clause Yes Details →
5.5.4 20 Oct 2026 U2 BSD-3-Clause Yes Details →
6.1.0 14 Oct 2026 U2 BSD-3-Clause Yes Details →
5.5.3 14 Oct 2026 U2 BSD-3-Clause Yes Details →
6.0.1 14 Sep 2026 U2 BSD-3-Clause Yes Details →
6.0.0 01 Sep 2026 U2 BSD-3-Clause Yes Details →
5.5.2 01 Sep 2026 U2 BSD-3-Clause Yes Details →
6.0.0b3 24 Aug 2026 U2 BSD-3-Clause Yes Details →
6.0.0b2 14 Aug 2026 U2 BSD-3-Clause Yes Details →
6.0.0b1 13 Aug 2026 U2 BSD-3-Clause Yes Details →
5.5.1 10 Aug 2026 U2 BSD-3-Clause Yes Details →
5.5.0 10 Jun 2026 U2 BSD-3-Clause Yes Details →
5.4.6 05 May 2026 M1 U1 BSD-3-Clause Yes Details →
5.4.5 28 Apr 2026 M1 U1 BSD-3-Clause Yes Details →
5.4.4 26 Mar 2026 M2 U2 BSD-3-Clause Yes Details →
5.4.3 12 Dec 2025 M3 U3 BSD-3-Clause Yes Details →
5.4.2 24 Oct 2025 M3 U3 BSD-3-Clause Yes Details →
5.4.1 17 Oct 2025 M3 U3 BSD-3-Clause Yes Details →
5.4.0 06 Oct 2025 M3 U3 BSD-3-Clause Yes Details →
5.3.0 15 Apr 2025 M3 U3 BSD-3-Clause Yes Details →
5.3.0rc0 07 Apr 2025 M3 U3 BSD-3-Clause Yes Details →
5.2.1 21 Oct 2024 M3 U4 BSD-3-Clause Yes Details →
5.2.0 01 Oct 2024 M3 U4 BSD-3-Clause Yes Details →
5.1.0 31 Jul 2024 M3 U4 BSD-3-Clause Yes Details →
4.1.6 31 Jul 2024 M3 U4 non-standard Yes Details →
5.0.0 24 May 2024 M3 U4 BSD-3-Clause Yes Details →
5.0.0b2 09 May 2024 M3 U4 BSD-3-Clause Yes Details →
5.0.0b1 22 Apr 2024 M3 U4 BSD-3-Clause Yes Details →
4.1.5 04 Apr 2024 H1 M3 U5 non-standard Yes Details →
4.1.4 30 Mar 2024 H1 M3 U5 non-standard Yes Details →
4.1.3 26 Mar 2024 H1 M3 U5 non-standard Yes Details →
4.1.2 25 Mar 2024 H1 M3 U5 non-standard Yes Details →
4.1.1 23 Mar 2024 H1 M3 U5 non-standard Yes Details →
4.1.0 20 Mar 2024 H1 M3 U5 non-standard Yes Details →
4.0.2 10 Aug 2023 H2 M2 U5 non-standard Yes Details →
4.0.1 08 Jun 2023 H2 M2 U5 non-standard Yes Details →
4.0.0 20 Apr 2023 H2 M2 U5 non-standard Yes Details →
4.0.0b2 15 Mar 2023 H2 M2 U5 non-standard Yes Details →
4.0.0b1 01 Mar 2023 H2 M2 U5 non-standard Yes Details →
3.1.1 27 Jan 2023 H2 M2 U5 non-standard Yes Details →
3.1.0 05 Dec 2022 H2 M2 U5 non-standard Yes Details →
1.5.1 05 Dec 2022 H2 M2 U5 non-standard Yes Details →
3.0.0 09 Sep 2022 H2 M2 U5 non-standard Yes Details →
3.0.0b1 02 Aug 2022 H2 M2 U5 non-standard Yes Details →
2.3.1 06 Jun 2022 H2 M2 U5 non-standard Yes Details →
2.3.0 06 May 2022 H2 M2 U5 non-standard Yes Details →
2.2.2 14 Mar 2022 H2 M2 U5 non-standard Yes Details →
2.2.1 11 Mar 2022 H2 M2 U5 non-standard Yes Details →
2.2.0 07 Mar 2022 H2 M2 U5 non-standard Yes Details →
2.1.1 25 Jan 2022 H2 M2 U5 non-standard Yes Details →
2.1.0 21 Jan 2022 H2 M2 U5 non-standard Yes Details →
2.0.2 10 Jan 2022 H2 M2 U5 non-standard Yes Details →
2.0.1 22 Dec 2021 H2 M2 U5 non-standard Yes Details →
2.0.0 01 Dec 2021 H2 M2 U5 non-standard Yes Details →
2.0.0rc5 26 Nov 2021 H2 M2 U5 non-standard Yes Details →
2.0.0rc4 18 Nov 2021 H2 M2 U5 non-standard Yes Details →
2.0.0rc3 04 Nov 2021 H2 M2 U5 non-standard Yes Details →
1.5.0 04 Nov 2021 H2 M2 U5 non-standard Yes Details →
2.0.0rc2 30 Oct 2021 H2 M2 U5 non-standard Yes Details →
2.0.0rc1 30 Oct 2021 H2 M2 U5 non-standard Yes Details →
2.0.0b3 14 Oct 2021 H2 M2 U5 non-standard Yes Details →
2.0.0b2 29 Sep 2021 H2 M2 U5 non-standard Yes Details →
2.0.0b1 17 Sep 2021 H2 M2 U5 non-standard Yes Details →
1.4.2 16 Jul 2021 H2 M3 U6 non-standard Yes Details →
1.4.1 12 May 2021 H2 M3 U6 non-standard Yes Details →
1.4.0 19 Apr 2021 H2 M3 U6 non-standard Yes Details →
1.3.0 11 Dec 2020 H2 M3 U6 non-standard Yes Details →
1.2.2 27 Nov 2020 H2 M3 U6 non-standard Yes Details →
1.2.1 30 Oct 2020 H2 M3 U6 non-standard Yes Details →
1.2.0 29 Oct 2020 H2 M3 U6 non-standard Yes Details →
1.2.0b1 16 Oct 2020 H2 M3 U6 non-standard Yes Details →
1.1.0 17 Jan 2020 H2 M5 U7 non-standard Yes Details →
1.1.0b1 26 Dec 2019 H2 M5 U7 non-standard Yes Details →
1.0.0 03 May 2019 H2 M5 U7 non-standard Yes Details →
1.0.0b2 09 Apr 2019 H2 M4 U6 non-standard Yes Details →
0.9.6 01 Apr 2019 H2 M4 U6 non-standard Yes Details →
0.9.5 28 Mar 2019 H2 M4 U7 non-standard Yes Details →
1.0.0b1 27 Mar 2019 H2 M4 U6 non-standard Yes Details →
0.9.4 24 Sep 2018 H2 M4 U7 non-standard Yes Details →
0.9.3 12 Sep 2018 H2 M4 U7 non-standard Yes Details →
0.9.2 11 Aug 2018 H2 M4 U7 non-standard Yes Details →
0.9.1 04 Jul 2018 H2 M4 U7 non-standard Yes Details →
0.9.0 15 Jun 2018 H2 M4 U7 non-standard Yes Details →
0.9.0rc1 12 Jun 2018 H2 M4 U7 non-standard Yes Details →
0.9.0b3 23 May 2018 H2 M4 U7 non-standard Yes Details →
0.9.0b2 15 May 2018 H2 M4 U7 non-standard Yes Details →
0.9.0b1 07 May 2018 H2 M4 U7 non-standard Yes Details →
0.8.1 07 Nov 2017 H2 M4 U7 non-standard Yes Details →
0.8.0 03 Oct 2017 H2 M4 U7 non-standard Yes Details →
0.8.0rc2 25 Sep 2017 H2 M4 U7 non-standard Yes Details →
0.8.0rc1 19 Sep 2017 H2 M4 U7 non-standard Yes Details →
0.8.0b5 08 Sep 2017 H2 M4 U7 non-standard Yes Details →
0.8.0b4 31 Aug 2017 H2 M4 U7 non-standard Yes Details →
0.8.0b3 26 Aug 2017 H2 M4 U7 non-standard Yes Details →
0.8.0b2 20 Aug 2017 H2 M4 U7 non-standard Yes Details →
0.8.0b1 15 Aug 2017 H2 M4 U7 non-standard Yes Details →
0.7.2 10 Jan 2017 H2 M4 U7 non-standard Yes Details →
0.7.1 02 Jan 2017 H2 M4 U7 non-standard Yes Details →
0.7.0 02 Dec 2016 H2 M4 U7 non-standard Yes Details →
0.7.0b1 13 Nov 2016 H2 M4 U7 non-standard Yes Details →
0.6.1 04 May 2016 H2 M4 U7 — Yes Details →
0.6.0 25 Apr 2016 H2 M4 U7 — Yes Details →
0.5.0 08 Mar 2016 H2 M4 U7 — Yes Details →
0.4.1 03 Feb 2016 H2 M4 U7 — Yes Details →
0.4.0 01 Feb 2016 H2 M4 U7 — Yes Details →
0.3.0 04 Nov 2015 H2 M4 U7 — Yes Details →
0.2.0 12 Jul 2015 H2 M4 U7 — Yes Details →
0.1.0 08 Mar 2015 H2 M4 U7 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2021 3
  • 2022 2
  • 2024 3
  • 2026 8

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

03 Vulnerabilities

Recorded vulnerabilities for jupyterhub

The 5 most severe of 17 vulnerabilities recorded for this package

Search all 17 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2018-7206: JupyterHub OAuthenticator Group Whitelisting Bypass Vulnerability 8.8 high 1845c0e4b1bff3462c91c3108c85205acd3c75a2 18 Feb 2018
CVE-2024-28233: JupyterHub Cross-Site Scripting (XSS) via Cookie Tossing 8.1 high 4.1.0 07 Jul 2026
CVE-2024-28233: Cross Site Scripting (XSS) in JupyterHub via Self-XSS leveraged by Cookie Tossing 8.1 high 4.1.0 28 Mar 2024
CVE-2024-41942: JupyterHub Privilege Escalation Vulnerability 7.2 high 99e2720b0fc626cbeeca3c6337f917fdacfaa428 08 Aug 2024
CVE-2024-41942: Privilege Escalation Vulnerability in JupyterHub 7.2 high 4.1.6 08 Aug 2024

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 jupyterhub

Is jupyterhub safe to use?

Vulert records 17 vulnerabilities for jupyterhub in PyPI: 0 critical, 2 high, 6 medium and 0 low, plus 9 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 jupyterhub's Vulert package health score?

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

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

How many vulnerabilities does jupyterhub have?

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

8 vulnerabilities were recorded for jupyterhub in the last 12 months, and the oldest entry in this database dates to 18 Feb 2018. 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 jupyterhub 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 jupyterhub for upcoming vulnerabilities?

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