How severe is CVE-2025-32428?

CVE-2025-32428 has a CVSS 4.0 base score of 9.0, rated critical severity.

Is CVE-2025-32428 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (54th percentile), an estimate of the probability of exploitation in the next 30 days.

How do I fix CVE-2025-32428?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.

Does CVE-2025-32428 have an EU (EUVD) identifier?

Yes. CVE-2025-32428 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-10836.

When was CVE-2025-32428 published?

CVE-2025-32428 was published on 2025-04-15 and last updated on 2026-06-17.

CVE-2025-32428

CVE-2025-32428 is a critical-severity vulnerability with a CVSS 4.0 base score of 9.0. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-668.

Key facts

Severity: Critical (CVSS 4.0 base score 9.0)
EPSS exploit prediction: 1% (54th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2025-10836
Weakness: CWE-668
Published: 2025-04-15
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2025-32428?: 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.
How severe is CVE-2025-32428?: CVE-2025-32428 has a CVSS 4.0 base score of 9.0, rated critical severity.
Is CVE-2025-32428 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (54th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2025-32428?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2025-32428 have an EU (EUVD) identifier?: Yes. CVE-2025-32428 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-10836.
When was CVE-2025-32428 published?: CVE-2025-32428 was published on 2025-04-15 and last updated on 2026-06-17.

References

Other CWE-668 (Exposure of Resource to Wrong Sphere) vulnerabilities

CVE-2025-2857 — Critical (CVSS 10.0): Following the recent Chrome sandbox escape (CVE-2025-2783), various Firefox developers identified a similar pattern in…
CVE-2019-8779 — Critical (CVSS 10.0): A logic issue applied the incorrect restrictions. This issue was addressed by updating the logic to apply the correct…
CVE-2012-1846 — Critical (CVSS 10.0): Google Chrome 17.0.963.66 and earlier allows remote attackers to bypass the sandbox protection mechanism by leveraging…
CVE-2022-43684 — Critical (CVSS 9.9): ServiceNow has released patches and an upgrade that address an Access Control List (ACL) bypass issue in ServiceNow…
CVE-2022-24900 — Critical (CVSS 9.9): Piano LED Visualizer is software that allows LED lights to light up as a person plays a piano connected to a computer.…
CVE-2019-16541 — Critical (CVSS 9.9): Jenkins JIRA Plugin 3.0.10 and earlier does not declare the correct (folder) scope for per-folder Jira site…

Browse all CWE-668 (Exposure of Resource to Wrong Sphere) vulnerabilities →