| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-m68r-v472-jgq9 | JupyterHub has cross-origin form POSTs bypass XSRF (CWE-352) |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 26 May 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Fri, 22 May 2026 21:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Jupyterhub
Jupyterhub jupyterhub |
|
| Vendors & Products |
Jupyterhub
Jupyterhub jupyterhub |
Fri, 22 May 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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. | |
| Title | JupyterHub: Cross-origin form POSTs bypass XSRF | |
| Weaknesses | CWE-352 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-26T13:13:51.723Z
Reserved: 2026-04-15T15:57:41.717Z
Link: CVE-2026-40864
Updated: 2026-05-26T13:13:48.331Z
Status : Undergoing Analysis
Published: 2026-05-22T21:16:43.177
Modified: 2026-05-26T20:03:31.723
Link: CVE-2026-40864
No data.
OpenCVE Enrichment
Updated: 2026-05-22T21:30:16Z
Github GHSA