https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Wed, 07 Oct 2026 06:22:45 +0000 https://cve.radiocsirt.org/vuln/bdu:2025-10399 bdu:2025-10399 https://cve.radiocsirt.org/vuln/bdu:2025-10399 https://cve.radiocsirt.org/vuln/euvd-2026-229320 EUVD-2026-229320 https://cve.radiocsirt.org/vuln/euvd-2026-229320 https://cve.radiocsirt.org/vuln/fkie_cve-2025-32428 <p>Jupyter Remote Desktop Proxy allows you to run a Linux Desktop on a JupyterHub. jupyter-remote-desktop-proxy was meant to rely on UNIX sockets readable only by the current user since version 3.0.0, but when used with TigerVNC, the VNC server started by jupyter-remote-desktop-proxy were still accessible via the network. This vulnerability does not affect users having TurboVNC as the vncserver executable. This issue is fixed in 3.0.1.</p> <p>Jupyter Remote Desktop Proxy allows you to run a Linux Desktop on a JupyterHub. jupyter-remote-desktop-proxy was meant to rely on UNIX sockets readable only by the current user since version 3.0.0, but when used with TigerVNC, the VNC server started by jupyter-remote-desktop-proxy were still accessible via the network. This vulnerability does not affect users having TurboVNC as the vncserver executable. This issue is fixed in 3.0.1.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2025-32428 https://cve.radiocsirt.org/vuln/ghsa-vrq4-9hc3-cgp7 <p><strong>Affected:</strong> PyPI: jupyter-remote-desktop-proxy</p> <p>## Summary</p> <p>`jupyter-remote-desktop-proxy` was meant to rely on UNIX sockets readable only by the current user since version 3.0.0, but when used with TigerVNC, the VNC server started by `jupyter-remote-desktop-proxy` were still accessible via the network.</p> <p>This vulnerability does not affect users having TurboVNC as the `vncserver` executable.</p> <p>## Credits</p> <p>This vulnerability was identified by Arne Gottwald at University of Göttingen and analyzed, reported, and reviewed by @frejanordsiek.</p> <p><strong>Affected:</strong> PyPI: jupyter-remote-desktop-proxy</p> <p>## Summary</p> <p>`jupyter-remote-desktop-proxy` was meant to rely on UNIX sockets readable only by the current user since version 3.0.0, but when used with TigerVNC, the VNC server started by `jupyter-remote-desktop-proxy` were still accessible via the network.</p> <p>This vulnerability does not affect users having TurboVNC as the `vncserver` executable.</p> <p>## Credits</p> <p>This vulnerability was identified by Arne Gottwald at University of Göttingen and analyzed, reported, and reviewed by @frejanordsiek.</p> https://cve.radiocsirt.org/vuln/ghsa-vrq4-9hc3-cgp7 https://cve.radiocsirt.org/vuln/pysec-2026-365 <p><strong>Affected:</strong> PyPI: jupyter-remote-desktop-proxy</p> <p>## Summary</p> <p>`jupyter-remote-desktop-proxy` was meant to rely on UNIX sockets readable only by the current user since version 3.0.0, but when used with TigerVNC, the VNC server started by `jupyter-remote-desktop-proxy` were still accessible via the network.</p> <p>This vulnerability does not affect users having TurboVNC as the `vncserver` executable.</p> <p>## Credits</p> <p>This vulnerability was identified by Arne Gottwald at University of Göttingen and analyzed, reported, and reviewed by @frejanordsiek.</p> <p><strong>Affected:</strong> PyPI: jupyter-remote-desktop-proxy</p> <p>## Summary</p> <p>`jupyter-remote-desktop-proxy` was meant to rely on UNIX sockets readable only by the current user since version 3.0.0, but when used with TigerVNC, the VNC server started by `jupyter-remote-desktop-proxy` were still accessible via the network.</p> <p>This vulnerability does not affect users having TurboVNC as the `vncserver` executable.</p> <p>## Credits</p> <p>This vulnerability was identified by Arne Gottwald at University of Göttingen and analyzed, reported, and reviewed by @frejanordsiek.</p> https://cve.radiocsirt.org/vuln/pysec-2026-365