Answer in brief
CVE-2025-32428 records a Critical severity (CVSS 0.0) vulnerability in TigerVNC accessible via the network and not just via a UNIX socket as intended. The current sources do not mark it as known exploited. The current feed maps jupyter-remote-desktop-proxy (pip), jupyter-remote-desktop-proxy (pypi). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 0.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps jupyter-remote-desktop-proxy (pip), jupyter-remote-desktop-proxy (pypi). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| jupyter-remote-desktop-proxypip | =3.0.0 | 3.0.1 |
| jupyter-remote-desktop-proxypypi | >=3.0.0 <3.0.1 | 3.0.1 |
Published upstream
Apr 12, 2025
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Oct 27, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Oct 27, 2026
## 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.
Quoted source text, attributed separately from HOL analysis.