---
id: "CVE-2025-32428"
kind: "vulnerability"
aliases: ["CVE-2025-32428", "GHSA-vrq4-9hc3-cgp7"]
title: "TigerVNC accessible via the network and not just via a UNIX socket as intended"
severity: "critical"
cvss: 9.0
epss: 0.00916
exploited: false
status: "open"
category: "package"
products: [{"name": "jupyter-remote-desktop-proxy", "fixed": ["3.0.1"], "affected": "= 3.0.0", "ecosystem": "pypi"}]
ecosystems: ["pypi"]
tags: ["cwe-668", "jupyter", "jupyterhub", "package", "python", "self-hosted"]
not_affected_if: ["loopback-only-network", "non-3.0.0-version", "turbovnc"]
published_at: "2025-04-12T03:42:31+00:00"
first_seen_at: "2026-10-27T17:27:29+00:00"
updated_at: "2026-10-27T17:32:47+00:00"
sources: [{"source": "ghsa", "url": "https://github.com/advisories/GHSA-vrq4-9hc3-cgp7", "first_seen_at": "2026-10-27T17:27:29+00:00"}, {"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2025-32428", "first_seen_at": "2026-10-27T17:32:47+00:00"}]
---

# TigerVNC accessible via the network and not just via a UNIX socket as intended

jupyter-remote-desktop-proxy 3.0.0 was meant to expose the VNC server only over a UNIX socket readable by the current user, but with TigerVNC the VNC server still listens on the network. A network attacker who can reach that port can connect to the remote desktop session without going through Jupyter's authentication.

_Summary, check and fix written by a model from the sources; labelled as such._

## Affected

- pypi:jupyter-remote-desktop-proxy affected = 3.0.0 fixed 3.0.1

## How to check

- Run `pip show jupyter-remote-desktop-proxy` and confirm the installed version is `3.0.0`
- Check whether the `vncserver` on the path is TigerVNC rather than TurboVNC, for example with `vncserver -version`
- Check whether the VNC port is listening on a non-loopback address, for example with `ss -ltnp`

## Fix

- Upgrade jupyter-remote-desktop-proxy to `3.0.1`
- Until the upgrade is done, block the VNC port at the host or network firewall

## Timeline

- 2026-10-27T17:27:29+00:00 ghsa https://github.com/advisories/GHSA-vrq4-9hc3-cgp7
- 2026-10-27T17:32:47+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2025-32428

## From the sources

## 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.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_