CVE-2025-32428 Jupyter Remote Desktop Proxy makes TigerVNC accessible via the network and not just via a UNIX socket as intended
Attackers can access TigerVNC sessions over the network instead of just via UNIX sockets, bypassing intended access controls in Jupyter Remote Desktop Proxy.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Local or same network only
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2025-32428?
CVE-2025-32428 is a critical vulnerability in jupyterhub jupyter-remote-desktop-proxy, published on 14 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Official description
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.
Weakness: CWE-668
Which versions are affected by CVE-2025-32428?
3 open source packages ship an affected version, including jupyter-remote-desktop-proxy.
| Package | Affected | Fixed in |
|---|---|---|
jupyter-remote-desktop-proxy PyPI | From 3.0.0 | 3.0.1 |
jupyter-remote-desktop-proxy PyPI | From 3.0.0 | 3.0.1 |
jupyter-remote-desktop-proxy PyPI | From 3.0.0 | 3.0.1 |
How do I fix CVE-2025-32428?
Upgrade jupyter-remote-desktop-proxy to 3.0.1 or later.
Is CVE-2025-32428 being exploited?
There is no known exploitation of CVE-2025-32428 in the wild and no public exploit code.
Sources
Also known as GHSA-vrq4-9hc3-cgp7, PYSEC-2026-365.