Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The PyPI package jupyter-remote-desktop-proxy versions 3.0.0 up to but not including 3.0.1 is affected. Although version 3.0.0 was meant to restrict the TigerVNC server it starts to UNIX sockets readable only by the current user, the VNC server remains reachable over the network. The source does not describe the attacker's required access or the exact impact. The package is fixed in 3.0.1, so users should upgrade to that version. Installations using TurboVNC as the vncserver executable are not affected.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 9.0 | Critical | 4.0 | CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0094, the 61st percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 31 Oct 2026, 14:07 UTC First seen by agentprime
- 31 Oct 2026, 14:07 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-vrq4-9hc3-cgp7
- OSV: GHSA-vrq4-9hc3-cgp7
- github.com/jupyterhub/jupyter-remote-desktop-proxy/security/advisories/GHSA-vrq4-9hc3-cgp7
- nvd.nist.gov/vuln/detail/CVE-2025-32428
- github.com/jupyterhub/jupyter-remote-desktop-proxy/commit/7dd54c25a4253badd8ea68895437e5a66a59090d
- github.com/jupyterhub/jupyter-remote-desktop-proxy
- github.com/pypa/advisory-database/tree/main/vulns/jupyter-remote-desktop-proxy/PYSEC-2026-365.yaml
- pypi.org/project/jupyter-remote-desktop-proxy