Which versions of jupyter-remote-desktop-proxy are affected by CVE-2025-32428?

jupyter-remote-desktop-proxy (pip) versions = 3.0.0 is affected.

Is there a fix for CVE-2025-32428?

Yes. CVE-2025-32428 is fixed in 3.0.1. Upgrade to this version or later.

Is CVE-2025-32428 exploitable, and should I be worried?

Whether CVE-2025-32428 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk.

What actually determines whether CVE-2025-32428 is exploitable, and how bad it is?

Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.

CVE-2025-32428 in jupyter-remote-desktop-proxy

Q: How do I fix CVE-2025-32428?

Upgrade jupyter-remote-desktop-proxy to 3.0.1 or later.

CVE-2025-32428

CVE-2025-32428 is a critical-severity security vulnerability in jupyter-remote-desktop-proxy (pip), affecting versions = 3.0.0. It is fixed in 3.0.1.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!

Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

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

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.

Impact

Affected versions

jupyter-remote-desktop-proxy (= 3.0.0)

Security releases

jupyter-remote-desktop-proxy → 3.0.1 (pip)

Kodem intelligence

Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.

Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.

Already deployed Kodem?

See it in your environment New to Kodem? Get a demo →

Remediation advice

Upgrade jupyter-remote-desktop-proxy to 3.0.1 or later to resolve this vulnerability.

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

What is CVE-2025-32428? CVE-2025-32428 is a critical-severity security vulnerability in jupyter-remote-desktop-proxy (pip), affecting versions = 3.0.0. It is fixed in 3.0.1.
Which versions of jupyter-remote-desktop-proxy are affected by CVE-2025-32428? jupyter-remote-desktop-proxy (pip) versions = 3.0.0 is affected.
Is there a fix for CVE-2025-32428? Yes. CVE-2025-32428 is fixed in 3.0.1. Upgrade to this version or later.
Is CVE-2025-32428 exploitable, and should I be worried? Whether CVE-2025-32428 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
What actually determines whether CVE-2025-32428 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
How do I fix CVE-2025-32428? Upgrade jupyter-remote-desktop-proxy to 3.0.1 or later.