Skip to content
Patch Next
Sign inAdd to your agent

← Public intelligence

PyPI package

jupyter-remote-desktop-proxy

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

1 actionable advisory, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. Critical, CVSS 9.0PyPIAmendedPublished

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

    CVE-2025-32428 · GHSA-vrq4-9hc3-cgp7

    Affected
    • PyPI jupyter-remote-desktop-proxy >= 3.0.0, < 3.0.1
    Fixed in
    3.0.1· Vendor fix available
    Issue
    `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.

    Recommended action: Upgrade to 3.0.1 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →