https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sun, 04 Oct 2026 02:20:52 +0000 https://cve.radiocsirt.org/vuln/cve-2026-40864 <p><strong>Affected:</strong> jupyterhub</p> <p>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&#39;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.</p> <p><strong>Affected:</strong> jupyterhub</p> <p>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&#39;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.</p> https://cve.radiocsirt.org/vuln/cve-2026-40864 https://cve.radiocsirt.org/vuln/ghsa-m68r-v472-jgq9 <p><strong>Affected:</strong> PyPI: jupyterhub</p> <p>## Summary</p> <p>JupyterHub&#39;s XSRF protection (updated in 4.1.0) inappropriately treated requests with `Sec-Fetch-Mode: no-cors` as same-origin requests, which they are not, 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&#39;s server.</p> <p>## Patches</p> <p>Upgrade to JupyterHub 5.4.5.</p> <p>## Mitigations</p> <p>If a reverse proxy is in use, drop requests to JupyterHub with `Sec-Fetch-Mode: no-cors`.</p> <p><strong>Affected:</strong> PyPI: jupyterhub</p> <p>## Summary</p> <p>JupyterHub&#39;s XSRF protection (updated in 4.1.0) inappropriately treated requests with `Sec-Fetch-Mode: no-cors` as same-origin requests, which they are not, 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&#39;s server.</p> <p>## Patches</p> <p>Upgrade to JupyterHub 5.4.5.</p> <p>## Mitigations</p> <p>If a reverse proxy is in use, drop requests to JupyterHub with `Sec-Fetch-Mode: no-cors`.</p> https://cve.radiocsirt.org/vuln/ghsa-m68r-v472-jgq9