CVE-2025-32428: TigerVNC accessible via the network and not just via a UNIX socket as intended
(updated )
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.
References
- github.com/advisories/GHSA-vrq4-9hc3-cgp7
- github.com/jupyterhub/jupyter-remote-desktop-proxy
- github.com/jupyterhub/jupyter-remote-desktop-proxy/commit/7dd54c25a4253badd8ea68895437e5a66a59090d
- github.com/jupyterhub/jupyter-remote-desktop-proxy/security/advisories/GHSA-vrq4-9hc3-cgp7
- nvd.nist.gov/vuln/detail/CVE-2025-32428
Code Behaviors & Features
Detect and mitigate CVE-2025-32428 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →