{"id":"CVE-2025-32428","aliases":["EUVD-2025-10836","GHSA-vrq4-9hc3-cgp7","PYSEC-2026-365"],"status":"published","title":"Jupyter Remote Desktop Proxy makes TigerVNC accessible via the network and not just via a UNIX socket as intended","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.","severity":{"version":"4.0","score":9,"vector":"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","level":"critical","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-09","score":0.00935,"percentile":0.61026,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-668"],"published":"2025-04-12T03:42:31Z","modified":"2026-10-28T02:30:47Z","fixes":[{"ecosystem":"PyPI","package":"jupyter-remote-desktop-proxy","fixed_in":["3.0.1"],"sources":["ghsa","osv"]}],"affected":[{"source":"ghsa","ecosystem":"PyPI","package":"jupyter-remote-desktop-proxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"last_affected":"3.0.0"},{"fixed":"3.0.1"}]}],"versions":["3.0.0"]},{"source":"osv","ecosystem":"PyPI","package":"jupyter-remote-desktop-proxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.1"}]}],"versions":["3.0.0"]},{"source":"osv","ecosystem":"PyPI","package":"jupyter-remote-desktop-proxy","ranges":[{"type":"ECOSYSTEM","events":[{"introduced":"3.0.0"},{"fixed":"3.0.1"}]}],"versions":["3.0.0"]}],"products":[{"vendor":"jupyterhub","product":"jupyter-remote-desktop-proxy"}],"references":[{"url":"https://github.com/jupyterhub/jupyter-remote-desktop-proxy/security/advisories/GHSA-vrq4-9hc3-cgp7","tags":["x_refsource_CONFIRM","advisory","web"]},{"url":"https://github.com/jupyterhub/jupyter-remote-desktop-proxy/commit/7dd54c25a4253badd8ea68895437e5a66a59090d","tags":["x_refsource_MISC","fix","web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2025-32428","tags":["advisory"]},{"url":"https://github.com/pypa/advisory-database/tree/main/vulns/jupyter-remote-desktop-proxy/PYSEC-2026-365.yaml","tags":["web"]},{"url":"https://pypi.org/project/jupyter-remote-desktop-proxy","tags":["web","package"]},{"url":"https://github.com/advisories/GHSA-vrq4-9hc3-cgp7","tags":["advisory"]},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/32xxx/CVE-2025-32428.json","tags":["advisory"]},{"url":"https://github.com/jupyterhub/jupyter-remote-desktop-proxy","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2025-32428","title":"Jupyter Remote Desktop Proxy makes TigerVNC accessible via the network and not just via a UNIX socket as intended","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.","status":"published","published":"2025-04-14T23:29:40.494Z","modified":"2025-04-15T02:54:15.365Z","cvss":[{"version":"4.0","score":9,"vector":"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","level":"critical","assessor":"cna"}],"cwes":["CWE-668"],"updated_at":"2026-11-02T14:32:46.42892Z"}],"euvd":[{"id":"EUVD-2025-10836","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.","status":"published","published":"2025-04-14T23:29:40Z","modified":"2025-04-15T02:54:15Z","cvss":[{"version":"4.0","score":9,"vector":"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","level":"critical"}],"updated_at":"2026-11-02T20:52:32.064592Z"}],"ghsa":[{"id":"GHSA-vrq4-9hc3-cgp7","title":"TigerVNC accessible via the network and not just via a UNIX socket as intended","description":"## Summary\n\n`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.\n\nThis vulnerability does not affect users having TurboVNC as the `vncserver` executable.\n\n## Credits\n\nThis vulnerability was identified by Arne Gottwald at University of Göttingen and analyzed, reported, and reviewed by @frejanordsiek.","status":"published","published":"2025-04-12T03:42:31Z","modified":"2026-10-27T17:24:28Z","cvss":[{"version":"4.0","score":9,"vector":"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","level":"critical"}],"cwes":["CWE-668"],"updated_at":"2026-11-02T14:41:38.969831Z"}],"nvd":[{"id":"CVE-2025-32428","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.","status":"published","published":"2025-04-15T00:15:14.88Z","modified":"2026-06-17T09:11:58.533Z","cvss":[{"version":"4.0","score":9,"vector":"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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X","level":"critical","assessor":"secondary"}],"cwes":["CWE-668"],"updated_at":"2026-11-02T14:11:00.456643Z"}],"osv":[{"id":"CVE-2025-32428","title":"Jupyter Remote Desktop Proxy makes TigerVNC accessible via the network and not just via a UNIX socket as intended","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.","status":"published","published":"2025-04-14T23:29:40.494Z","modified":"2026-10-28T02:30:47.735662754Z","cvss":[{"version":"4.0","score":9,"vector":"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","level":"critical"}],"cwes":["CWE-668"],"updated_at":"2026-11-02T15:44:48.02508Z"},{"id":"GHSA-vrq4-9hc3-cgp7","title":"TigerVNC accessible via the network and not just via a UNIX socket as intended","description":"## Summary\n\n`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.\n\nThis vulnerability does not affect users having TurboVNC as the `vncserver` executable.\n\n## Credits\n\nThis vulnerability was identified by Arne Gottwald at University of Göttingen and analyzed, reported, and reviewed by @frejanordsiek.","status":"published","published":"2025-04-12T03:42:31Z","modified":"2026-10-27T17:30:38.257646497Z","cvss":[{"version":"4.0","score":9,"vector":"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","level":"critical"}],"cwes":["CWE-668"],"updated_at":"2026-11-02T15:46:57.694388Z"},{"id":"PYSEC-2026-365","title":"TigerVNC accessible via the network and not just via a UNIX socket as intended","description":"## Summary\n\n`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.\n\nThis vulnerability does not affect users having TurboVNC as the `vncserver` executable.\n\n## Credits\n\nThis vulnerability was identified by Arne Gottwald at University of Göttingen and analyzed, reported, and reviewed by @frejanordsiek.","status":"published","published":"2026-06-29T11:50:35.87498Z","modified":"2026-07-01T20:22:54.84049Z","cvss":[{"version":"4.0","score":9,"vector":"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","level":"critical"}],"updated_at":"2026-11-02T15:52:56.847083Z"}]}}