Jupyterhub
8 CVEs tracked. None of them is in CISA KEV.
This hub aggregates every CVE we track for Jupyterhub, a product in the oss libraries space. Use it to gauge the current risk picture and drill into individual advisories.
Jupyterhub CVEs per month
| Month | CVEs |
|---|---|
| 2024-10 | 0 |
| 2024-11 | 0 |
| 2024-12 | 0 |
| 2025-01 | 0 |
| 2025-02 | 0 |
| 2025-03 | 0 |
| 2025-04 | 0 |
| 2025-05 | 0 |
| 2025-06 | 0 |
| 2025-07 | 0 |
| 2025-08 | 0 |
| 2025-09 | 0 |
| 2025-10 | 0 |
| 2025-11 | 0 |
| 2025-12 | 0 |
| 2026-01 | 0 |
| 2026-02 | 0 |
| 2026-03 | 0 |
| 2026-04 | 1 |
| 2026-05 | 1 |
| 2026-06 | 0 |
| 2026-07 | 0 |
| 2026-08 | 1 |
| 2026-09 | 0 |
Severity
How the 8 CVEs score on CVSS. Severity is not exploitation: KEV is counted above.
- High2
- Medium5
- Low1
Latest CVEs
The 8 most recently published vulnerabilities affecting Jupyterhub.
- CVE-2026-54338JupyterHub: Unauthenticated Denial of Service via Unbounded Username Logging on Failed Login5.3
- CVE-2026-40864JupyterHub: Cross-origin form POSTs bypass XSRF5.4
- CVE-2026-33709JupyterHub has an Open Redirect Vulnerability6.1
- CVE-2024-41942JupyterHub has a privilege escalation vulnerability with the `admin:users` scope7.2
- CVE-2024-28233XSS in JupyterHub via Self-XSS leveraged by Cookie Tossing8.1
- CVE-2021-41247incomplete logout in JupyterHub3.5
- CVE-2020-36191JupyterHub 1.1.0 allows CSRF in the admin panel via a request that lacks an _xsrf field, as demonstrated by a /hub/api/user request (to add or remove a user account).4.5
- CVE-2019-10255An Open Redirect vulnerability for all browsers in Jupyter Notebook before 5.7.7 and some browsers (Chrome, Firefox) in JupyterHub before 0.9.5 allows crafted links to the login page, which will re...6.1
Product grouping is registry-driven, with AI assist and human review. How it works