<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-04T02:20:54.824765+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-40864</id>
    <title>CVE-2026-40864 — JupyterHub: Cross-origin form POSTs bypass XSRF</title>
    <updated>2026-10-04T02:20:54.826513+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><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'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></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-40864"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-m68r-v472-jgq9</id>
    <title>GHSA-m68r-v472-jgq9 — JupyterHub has cross-origin form POSTs bypass XSRF (CWE-352)</title>
    <updated>2026-10-04T02:20:54.826596+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PyPI: jupyterhub</p>
<p>## Summary</p>
<p>JupyterHub'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'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></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-m68r-v472-jgq9"/>
  </entry>
</feed>
