https://cve.radiocsirt.org/rss/recent/all/10 Most recent entries from all 2026-10-19T01:04:51.514061+00:00 Vulnerability-Lookup csirt@opendfir.org python-feedgen Contains only the most 10 recent entries. https://cve.radiocsirt.org/vuln/cve-2022-21697 CVE-2022-21697 — SSRF vulnerability (requires authentication) 2026-10-19T01:04:51.515694+00:00

Affected: jupyterhub jupyter-server-proxy

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.

 https://cve.radiocsirt.org/vuln/ghsa-gcv9-6737-pjqw GHSA-gcv9-6737-pjqw — SSRF vulnerability in jupyter-server-proxy 2026-10-19T01:04:51.515752+00:00

Affected: PyPI: jupyter-server-proxy

### Impact

**What kind of vulnerability is it?** Server-Side Request Forgery ( SSRF )

**Who is impacted?** Any user deploying Jupyter Server or Notebook with jupyter-proxy-server extension enabled.

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.

### Patches

_Has the problem been patched? What versions should users upgrade to?_

Upgrade to 3.2.1, or apply the patch https://github.com/jupyterhub/jupyter-server-proxy/compare/v3.2.0...v3.2.1.patch

### For more information

If you have any questions or comments about this advisory:

* Open a topic [on our forum](https://discourse.jupyter.org) * Email the Jupyter security team at [security@ipython.org](mailto:security@ipython.org)