CVE-2026-40864
JupyterHub is software that allows users to create a multi-user …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/jupyterhub/jupyterhub/security/advisories/GHSA-m68r-v472-jgq9
- github.com/advisories/GHSA-m68r-v472-jgq9
- github.com/jupyterhub/jupyterhub/commit/9c5ec277d3cda5a59de2d8c8117efa77bd941127
- nvd.nist.gov/vuln/detail/CVE-2026-40864
- nvd.nist.gov/vuln/detail/CVE-2026-40864
- cve.org/CVERecord?id=CVE-2026-40864
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.