jupyter-remote-desktop-proxy
Affected
- introduced
3.0.0, fixed3.0.1(ecosystem)
Fixed versions
3.0.1
Fix
- Fixed version
3.0.1pip install --upgrade jupyter-remote-desktop-proxy==3.0.1
Advisory
Also known as: CVE-2025-32428, PYSEC-2026-365
TigerVNC accessible via the network and not just via a UNIX socket as intended
Summary
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.
Credits
This vulnerability was identified by Arne Gottwald at University of Göttingen and analyzed, reported, and reviewed by @frejanordsiek.
Critical Basis: The source's own band: CRITICAL
3.0.0, fixed 3.0.1 (ecosystem)3.0.1
3.0.1pip install --upgrade jupyter-remote-desktop-proxy==3.0.1Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0