Medium severity · published May 22, 2026
CVE-2026-40864
JupyterHub: Cross-origin form POSTs bypass XSRF
4.3
CVSS
0.1%
EPSS
No
On KEV
Description
JupyterHub is software that allows users to create a multi-user server for Jupyter notebooks. In versions 4.1.0 through 5.4.4, XSRF protection (updated in 4.1.0) inappropriately treated requests with Sec-Fetch-Mode: no-cors as same-origin requests, bypassing XSRF checks. The JSON API is not affected, only HTTP form endpoints, such as /hub/spawn and /hub/accept-share, meaning attackers could trigger server spawn (but not access the server) and if the attacker is a JupyterHub user permitted to share access to their server, cause a user to accept a share and have access to the attacker's server. This issue has been fixed in version 5.4.5. If developers are unable to immediately upgrade, they can temporarily mitigate this issue by dropping requests to JupyterHub with Sec-Fetch-Mode: no-cors if they are using a reverse proxy.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Confidentiality
None
Integrity
Low
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.1% · higher than 4% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
JU
jupyterhub · jupyterhub
>= 4.1.0, < 5.4.5 · source: vendor, NVD
Affected product
JU
jupyterhub
jupyterhub
More from jupyterhub
6.1
CVE-2026-33709
JupyterHub has an Open Redirect Vulnerability
5.3
CVE-2026-54338
JupyterHub: Unauthenticated Denial of Service via Unbounded Username Logging on Failed Login
4.2
CVE-2026-108752
JupyterHub through 6.0.1 OAuth Client ID Collision via Unescaped Hyphen