CVE-2025-32428Critical▾ MidnightTigerVNC accessible via the network and not just via a UNIX socket as intended
▾ Midnight zone — Critical, or high with PoC / in-the-wild
impact 52.3 · likelihood 0.2 · exploitation 0
Need a working PoC? Pro members can cast a request and our team develops one — it lands right here.
Disclosure to exploitation, from the record and what we observed since indexing it.
Disclosed via OSV
Last analysed / modified upstream
0.9%
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 vulnerability was identified by Arne Gottwald at University of Göttingen and analyzed, reported, and reviewed by @frejanordsiek.
jupyter-remote-desktop-proxy >= 3.0.0, < 3.0.1Upgrade to a patched release:
jupyter-remote-desktop-proxy 3.0.1Connected by shared product, vendor, weakness, or advisory.
CVE-2026-105754Medium· 6.5vLLM is an inference and serving engine for large language models
CVE-2026-105746Low· 2.2Docling simplifies document processing by parsing diverse formats and providing integrations with the generative AI ecosystem
CVE-2026-61590High· 7.4djust provides Phoenix LiveView-style reactive server-side rendering for Django with Rust-powered performance
CVE-2022-38474Medium· 4.3A website that had permission to access the microphone could record audio without the audio notification being shown
CVE-2026-57144High· 8.8PraisonAI SandlockSandbox falls back to unrestricted subprocess execution when Landlock is unavailable
CVE-2026-62204Medium· 6.6SiYuan versions before v3.7.4 fail to validate that packageName matches the downloaded package content in bazaar install endpoints