Skip to main content

Jupyterhub CVE-2026-33709

| EUVDEUVD-2026-18880 MEDIUM
URL Redirection to Untrusted Site (Open Redirect) (CWE-601)
2026-04-03 GitHub_M GHSA-3vff-hjqv-m7h8
5.1
CVSS 4.0 · Vendor: GitHub_M
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V3 - Web Frontend Security Redirect URL validation
MITRE ATT&CK

1 technique across 1 tactic: Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

This vulnerability presents moderate real-world risk. The CVSS score of 5.1 reflects low impact (confidentiality and integrity each scored as low), but the attack vector is network-based with low complexity and no authentication requirement. The presence of user interaction (UI:A) significantly reduces exploitability compared to fully automated attacks, placing it below critical severity thresholds. However, the practical attack scenario-phishing via a trusted JupyterHub domain-is credible and dangerous in educational and research environments where JupyterHub is commonly deployed. The lack of EPSS, KEV, or public POC data indicates this has not been demonstrated as actively exploited in the wild at scale, suggesting it remains primarily a patching priority rather than an emergency incident response scenario. Organizations should prioritize upgrading after patch release, particularly for public-facing JupyterHub instances.

Exploit ScenarioDerived

An attacker crafts a malicious link such as 'https://legitimate-jupyterhub.edu/hub/login?next=https://attacker.com/phishing' and distributes it via email to JupyterHub users, perhaps claiming it points to a course login page. When clicked, users see the legitimate JupyterHub login interface, enter their credentials, and are then redirected to an attacker-controlled phishing site that mimics JupyterHub's interface to harvest additional credentials or session tokens. The vulnerability bypasses JupyterHub's existing redirect check, making the attack appear seamlessly legitimate to users. No public exploit code has been identified, and the attack requires user interaction to succeed.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 03, 2026

Open redirect vulnerability in JupyterHub prior to version 5.4.4 allows unauthenticated remote attackers to craft malicious links that bypass JupyterHub's redirect validation, redirecting users through the legitimate login page to arbitrary attacker-controlled sites. This enables phishing attacks and credential harvesting by leveraging JupyterHub's trusted domain to establish credibility. The vulnerability requires user interaction (clicking a link) and has been patched in version 5.4.4.

RemediationAI

Vendor-released patch: upgrade JupyterHub to version 5.4.4 or later. This version includes the fix for the open redirect validation bypass. Organizations unable to upgrade immediately should consider implementing network-level controls to restrict login page access to trusted networks, or deploy a Web Application Firewall (WAF) rule to detect and block redirect parameters containing external domains. The patch is available via the official GitHub release at https://github.com/jupyterhub/jupyterhub/releases/tag/5.4.4 and through standard Python package management (pip install --upgrade jupyterhub>=5.4.4). Review the security advisory at https://github.com/jupyterhub/jupyterhub/security/advisories/GHSA-3vff-hjqv-m7h8 for comprehensive implementation guidance.

Affected VersionsENISA

jupyterhub < 5.4.4

Affected Packages

pypi jupyterhub fix: 5.4.4

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in pypi

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

JupyterHub implements URL redirect validation to prevent open redirect attacks (CWE-601), a common vulnerability class in web applications where user-supplied input controls redirect destinations without proper validation. The root cause is insufficient validation of the redirect parameter after login, allowing attackers to bypass the existing check by constructing specially crafted URLs. This vulnerability affects the authentication flow in JupyterHub's multi-user server architecture, where users are redirected after login. The CVSS vector indicates the attack requires network access (AV:N) with low complexity (AC:L) and no privileges (PR:N), but mandates user interaction (UI:A), suggesting the attacker must trick a user into clicking a malicious link.

Know when Jupyterhub gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (GitHub_M) PRIMARY 5.1 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (GitHub_M) · only source for this CVE.

CVSS VectorVendor: GitHub_M

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
None
User Interaction
Active
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
None
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch released
Apr 04, 2026 - 02:30 nvd
Patch available
CVE Published
Apr 03, 2026 - 22:00 nvd
MEDIUM 5.1

DescriptionCVE.org

JupyterHub is software that allows one to create a multi-user server for Jupyter notebooks. Prior to version 5.4.4, an open redirect vulnerability in JupyterHub allows attackers to construct links which, when clicked, take users to the JupyterHub login page, after which they are sent to an arbitrary attacker-controlled site outside JupyterHub instead of a JupyterHub page, bypassing JupyterHub's check to prevent this. This issue has been patched in version 5.4.4.

Threat Intelligence Overview

EPSS Score
0.0%
Top 87% exploitable
Threat Intel
1
1 source
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment GHSA GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0
CVE-2020-15110 HIGH POC
8.1 Jul 17

In jupyterhub-kubespawner before 0.12, certain usernames will be able to craft particular server names which will grant

CVE-2021-41194 CRITICAL
9.8 Oct 28

FirstUseAuthenticator is a JupyterHub authenticator that helps new users set their password on their first login to Jupy

CVE-2026-54338 MEDIUM POC
5.3 Aug 07

Log flooding via unbounded username input in JupyterHub's form-based login handler allows unauthenticated remote attacke

CVE-2026-33175 HIGH
8.8 Apr 03

Authentication bypass in JupyterHub OAuthenticator <17.4.0 allows authenticated attackers with unverified email addresse

CVE-2021-39160 HIGH
8.8 Aug 25

nbgitpuller is a Jupyter server extension to sync a git repository one-way to a local path. Rated high severity (CVSS 8.

CVE-2020-26261 HIGH
7.9 Dec 09

jupyterhub-systemdspawner enables JupyterHub to spawn single-user notebook servers using systemd. Rated high severity (C

CVE-2021-41247 HIGH
7.5 Nov 04

JupyterHub is an open source multi-user server for Jupyter notebooks. Rated high severity (CVSS 7.5), this vulnerability

CVE-2024-41942 HIGH
7.2 Aug 08

JupyterHub is software that allows one to create a multi-user server for Jupyter notebooks. Rated high severity (CVSS 7.

CVE-2024-28233 MEDIUM
6.1 Mar 27

JupyterHub is an open source multi-user server for Jupyter notebooks. Rated medium severity (CVSS 6.1), this vulnerabili

CVE-2019-10255 MEDIUM
6.1 Mar 28

An Open Redirect vulnerability for all browsers in Jupyter Notebook before 5.7.7 and some browsers (Chrome, Firefox) in

CVE-2026-108752 LOW
2.3 Oct 11

JupyterHub deployments through 6.0.1 that run in multi-user mode with the named-server feature enabled allow an authenti

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy