CyberSecBulletin

Jupyterhub vulnerabilities

We track 8 vulnerabilities in Jupyterhub products across 5 products. 8 are rated high or critical, and none are known to be exploited. The most recent was published on April 3, 2026.

8vulnerabilities
4critical
4high
0exploited
8.6average CVSS score

Latest Jupyterhub vulnerabilities

  • 8.8 High severity

    oauthenticator: Improper Authentication

    CVE-2026-33175Jupyterhub

    OAuthenticator is software that allows OAuth2 identity providers to be plugged in and used with JupyterHub. Prior to version 17.4.0, an authentication bypass vulnerability in oauthenticator allows an attacker with an unverified email address on an Auth0 tenant

  • 9.0 Critical severity

    jupyter-remote-desktop-proxy: Exposure of Resource to Wrong Sphere

    CVE-2025-32428Jupyterhub

    Jupyter Remote Desktop Proxy allows you to run a Linux Desktop on a JupyterHub. jupyter-remote-desktop-proxy was meant to rely on UNIX sockets readable only by the current user since version 3.0.0, but when used with TigerVNC, the VNC server started by jupyter

  • 9.8 Critical severity

    ltiauthenticator: Improper Verification of Cryptographic Signature

    CVE-2023-25574Jupyterhub

    `jupyterhub-ltiauthenticator` is a JupyterHub authenticator for learning tools interoperability (LTI). LTI13Authenticator that was introduced in `jupyterhub-ltiauthenticator` 1.3.0 wasn't validating JWT signatures. This is believed to allow the LTI13Authentica

  • 7.2 High severity

    jupyterhub: Improper Handling of Insufficient Privileges

    CVE-2024-41942Jupyterhub

    JupyterHub is software that allows one to create a multi-user server for Jupyter notebooks. Prior to versions 4.1.6 and 5.1.0, if a user is granted the `admin:users` scope, they may escalate their own privileges by making themselves a full admin user. The impa

  • 8.1 High severity

    oauthenticator: Incorrect Authorization

    CVE-2024-37300Jupyterhub

    OAuthenticator is software that allows OAuth2 identity providers to be plugged in and used with JupyterHub. JupyterHub < 5.0, when used with `GlobusOAuthenticator`, could be configured to allow all users from a particular institution only. This worked fine pri

  • 9.1 Critical severity

    oauthenticator: Improper Authorization

    CVE-2024-29033Jupyterhub

    OAuthenticator provides plugins for JupyterHub to use common OAuth providers, as well as base classes for writing one's own Authenticators with any OAuth 2.0 provider. `GoogleOAuthenticator.hosted_domain` is used to restrict what Google accounts can be authori

  • 9.8 Critical severity

    jupyter-server-proxy: Missing Authentication for Critical Functionality

    CVE-2024-28179JupyterhubEPSS 1.02%

    Jupyter Server Proxy allows users to run arbitrary external processes alongside their Jupyter notebook servers and provides authenticated web access. Prior to versions 3.2.3 and 4.1.1, Jupyter Server Proxy did not check user authentication appropriately when p

  • 7.1 High severity

    jupyter-server-proxy: Server-Side Request Forgery

    CVE-2022-21697JupyterhubEPSS 1.1%

    Jupyter Server Proxy is a Jupyter notebook server extension to proxy web services. Versions of Jupyter Server Proxy prior to 3.2.1 are vulnerable to Server-Side Request Forgery (SSRF). Any user deploying Jupyter Server or Notebook with jupyter-proxy-server ext