{"answers":{"affected":"3 open source packages ship an affected version, including jupyter-remote-desktop-proxy.","exploited":"There is no known exploitation of CVE-2025-32428 in the wild and no public exploit code.","fix":"Upgrade jupyter-remote-desktop-proxy to 3.0.1 or later.","what":"CVE-2025-32428 is a critical vulnerability in jupyterhub jupyter-remote-desktop-proxy, published on 14 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-32428 and fix it if it is affected.\n\nWhat it is: CVE-2025-32428 is a critical vulnerability in jupyterhub jupyter-remote-desktop-proxy, published on 14 Apr 2025. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-32428 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- jupyter-remote-desktop-proxy (PyPI): affected from 3.0.0; fixed in 3.0.1\n- jupyter-remote-desktop-proxy (PyPI): affected from 3.0.0; fixed in 3.0.1\n- jupyter-remote-desktop-proxy (PyPI): affected from 3.0.0; fixed in 3.0.1\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-32428/ (Markdown: https://insights.sbomify.com/CVE-2025-32428/index.md)","id":"CVE-2025-32428","markdown":"https://insights.sbomify.com/CVE-2025-32428/index.md","name":"CVE-2025-32428","record":{"aliases":["GHSA-vrq4-9hc3-cgp7","PYSEC-2026-365"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["security_bypass","data_read"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Jupyter remote desktop proxy","requires_auth":"none","summary":"Attackers can access TigerVNC sessions over the network instead of just via UNIX sockets, bypassing intended access controls in Jupyter Remote Desktop Proxy.","user_interaction":"not_required","vuln_class":"misconfiguration"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9,"severity":"critical","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-668","name":"Exposure of Resource to Wrong Sphere"}],"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.","ecosystems":["PyPI"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"Jupyter Remote Desktop Proxy makes TigerVNC accessible via the network and not just via a UNIX socket as intended","id":"CVE-2025-32428","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"PyPI","product":null,"products":[],"type":"misconfiguration","year":"2025"},"n_packages":3,"n_references":2,"next":{"headline":"XWiki Platform vulnerable to SQL injection through getdeleteddocuments.vm template sort parameter","id":"CVE-2025-32429"},"packages":[{"ecosystem":"PyPI","fixed":["3.0.1"],"introduced":["3.0.0"],"last_affected":[],"package":"jupyter-remote-desktop-proxy","purl":null,"source":"GHSA-vrq4-9hc3-cgp7"},{"ecosystem":"PyPI","fixed":["3.0.1"],"introduced":["3.0.0"],"last_affected":[],"package":"jupyter-remote-desktop-proxy","purl":"pkg:pypi/jupyter-remote-desktop-proxy","source":"GHSA-vrq4-9hc3-cgp7"},{"ecosystem":"PyPI","fixed":["3.0.1"],"introduced":["3.0.0"],"last_affected":[],"package":"jupyter-remote-desktop-proxy","purl":"pkg:pypi/jupyter-remote-desktop-proxy","source":"PYSEC-2026-365"}],"prev":{"headline":"Formie has a XSS vulnerability for importing forms","id":"CVE-2025-32427"},"products":["jupyter-remote-desktop-proxy"],"published":"2025-04-14","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CC BY 4.0","name":"PyPA Advisory Database","prefix":"PYSEC"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-04-15","vendors":["jupyterhub"]},"summary":"Attackers can access TigerVNC sessions over the network instead of just via UNIX sockets, bypassing intended access controls in Jupyter Remote Desktop Proxy.","url":"https://insights.sbomify.com/CVE-2025-32428/"}