Jupyter Remote Desktop Proxy makes TigerVNC accessible via the network and not just via a UNIX socket as intended
Priority MEDIUM 49CWE-668Published · Updated
Key facts
- Attack vector
- Adjacent network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Attack requirements
- Present
- Impact type
- —
- Confidentiality · integrity · availability
- High · High · High
- Fix status
- Fixed
Attack profile from CVSS 4.0 · CNA. Fix status from CNA and GitHub.
Summary
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.
Why it matters now
Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00935 60th percentileScored 2026-11-07
Fix Fixed jupyter-remote-desktop-proxy (jupyterhub): 3.0.1jupyter-remote-desktop-proxy (PyPI): 3.0.1
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| jupyterhub | jupyter-remote-desktop-proxy | 3.0.0 to before 3.0.1 | 3.0.1 | Patch available | CNA |
| — | jupyter-remote-desktop-proxy (PyPI) | 3.0.0 to before 3.0.1 | 3.0.1 | Patch available | GHSA-vrq4-9hc3-cgp7 |
- jupyter-remote-desktop-proxy Vendorjupyterhub Affected 3.0.0 to before 3.0.1 Fixed in 3.0.1 Patch available CNA
- jupyter-remote-desktop-proxy (PyPI) Vendor— Affected 3.0.0 to before 3.0.1 Fixed in 3.0.1 Patch available GHSA-vrq4-9hc3-cgp7
Remediation
- Fix · CNA jupyter-remote-desktop-proxy (jupyterhub) Fixed in 3.0.1
- Fix · GHSA-vrq4-9hc3-cgp7 jupyter-remote-desktop-proxy (PyPI) Fixed in 3.0.1 Advisory →
Timeline
- 2026-10-02 Threatist record created from CVE-2025-32428
- 2026-10-03 Alias added: GHSA-vrq4-9hc3-cgp7
References
Other 5
- https://github.com/jupyterhub/jupyter-remote-desktop-proxy/security/advisories/GHSA-vrq4-9hc3-cgp7
- https://github.com/jupyterhub/jupyter-remote-desktop-proxy/commit/7dd54c25a4253badd8ea68895437e5a66a59090d
- https://github.com/jupyterhub/jupyter-remote-desktop-proxy
- https://github.com/pypa/advisory-database/tree/main/vulns/jupyter-remote-desktop-proxy/PYSEC-2026-365.yaml
- https://pypi.org/project/jupyter-remote-desktop-proxy
More jupyterhub vulnerabilities
- TI-2023-10877 JupyterHub's LTI13Authenticator: JWT signature not validated CVSS 3.1CRITICAL 10.0
- TI-2021-16545 Remote code execution in Binderhub CVSS 3.1CRITICAL 9.8
- TI-2021-18033 Improper Access Control in jupyterhub-firstuseauthenticator CVSS 3.1CRITICAL 9.8
- TI-2021-16546 Code injection in nbgitpuller CVSS 3.1CRITICAL 9.6
- TI-2024-18755 Jupyter Server Proxy's Websocket Proxying does not require authentication CVSS 3.1CRITICAL 9.8
- TI-2024-23295 Jupyter Server Proxy has a reflected XSS issue in host parameter CVSS 3.1CRITICAL 9.7
Sources
- CVE-2025-32428 · CVE Program
- CVE-2025-32428 · NVD
- FIRST EPSS
- GHSA-vrq4-9hc3-cgp7 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences