https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Mon, 19 Oct 2026 01:04:51 +0000 https://cve.radiocsirt.org/vuln/cve-2022-21697 <p><strong>Affected:</strong> jupyterhub jupyter-server-proxy</p> <p>Jupyter Server Proxy is a Jupyter notebook server extension to proxy web services. Versions of Jupyter Server Proxy prior to 3.2.1 are vulnerable to Server-Side Request Forgery (SSRF). Any user deploying Jupyter Server or Notebook with jupyter-proxy-server extension enabled is affected. A lack of input validation allows authenticated clients to proxy requests to other hosts, bypassing the `allowed_hosts` check. Because authentication is required, which already grants permissions to make the same requests via kernel or terminal execution, this is considered low to moderate severity. Users may upgrade to version 3.2.1 to receive a patch or, as a workaround, install the patch manually.</p> <p><strong>Affected:</strong> jupyterhub jupyter-server-proxy</p> <p>Jupyter Server Proxy is a Jupyter notebook server extension to proxy web services. Versions of Jupyter Server Proxy prior to 3.2.1 are vulnerable to Server-Side Request Forgery (SSRF). Any user deploying Jupyter Server or Notebook with jupyter-proxy-server extension enabled is affected. A lack of input validation allows authenticated clients to proxy requests to other hosts, bypassing the `allowed_hosts` check. Because authentication is required, which already grants permissions to make the same requests via kernel or terminal execution, this is considered low to moderate severity. Users may upgrade to version 3.2.1 to receive a patch or, as a workaround, install the patch manually.</p> https://cve.radiocsirt.org/vuln/cve-2022-21697 https://cve.radiocsirt.org/vuln/ghsa-gcv9-6737-pjqw <p><strong>Affected:</strong> PyPI: jupyter-server-proxy</p> <p>### Impact</p> <p>**What kind of vulnerability is it?** Server-Side Request Forgery ( SSRF )</p> <p>**Who is impacted?** Any user deploying Jupyter Server or Notebook with jupyter-proxy-server extension enabled.</p> <p>A lack of input validation allowed authenticated clients to proxy requests to other hosts, bypassing the `allowed_hosts` check. Because authentication is required, which already grants permissions to make the same requests via kernel or terminal execution, this is considered low to moderate severity.</p> <p>### Patches</p> <p>_Has the problem been patched? What versions should users upgrade to?_</p> <p>Upgrade to 3.2.1, or apply the patch https://github.com/jupyterhub/jupyter-server-proxy/compare/v3.2.0...v3.2.1.patch</p> <p>### For more information</p> <p>If you have any questions or comments about this advisory:</p> <p>* Open a topic [on our forum](https://discourse.jupyter.org) * Email the Jupyter security team at [security@ipython.org](mailto:security@ipython.org)</p> <p><strong>Affected:</strong> PyPI: jupyter-server-proxy</p> <p>### Impact</p> <p>**What kind of vulnerability is it?** Server-Side Request Forgery ( SSRF )</p> <p>**Who is impacted?** Any user deploying Jupyter Server or Notebook with jupyter-proxy-server extension enabled.</p> <p>A lack of input validation allowed authenticated clients to proxy requests to other hosts, bypassing the `allowed_hosts` check. Because authentication is required, which already grants permissions to make the same requests via kernel or terminal execution, this is considered low to moderate severity.</p> <p>### Patches</p> <p>_Has the problem been patched? What versions should users upgrade to?_</p> <p>Upgrade to 3.2.1, or apply the patch https://github.com/jupyterhub/jupyter-server-proxy/compare/v3.2.0...v3.2.1.patch</p> <p>### For more information</p> <p>If you have any questions or comments about this advisory:</p> <p>* Open a topic [on our forum](https://discourse.jupyter.org) * Email the Jupyter security team at [security@ipython.org](mailto:security@ipython.org)</p> https://cve.radiocsirt.org/vuln/ghsa-gcv9-6737-pjqw