CVE-2026-128321
Tight JPEG decoding in TightVNC and UltraVNC viewers contains a heap-based buffer overflow because an attacker-controlled framebuffer rectangle width is not validated against a fixed-size decoding buffer. A malicious VNC server can cause an out-of-bounds heap write when a user connects, resulting in application crash and potentially other memory-corruption impacts.
Am I affected?
Sign in and add the software you use to your watchlist: we check it against every new vulnerability.
Show me how to fix itTimeline
- First covered by RedTeamDaily
- Published by NVD
- Last updated by NVD
Coverage
TightVNC and UltraVNC Viewer heap overflow can be triggered by a malicious VNC server
A heap-based buffer overflow in the Tight JPEG decoding of TightVNC Windows Viewer 1.3.10 and affected UltraVNC Windows Viewers lets a malicious VNC server send a crafted screen update that corrupts memory. Only denial of service was demonstrated, but arbitrary code execution with the viewer user's privileges may be possible. The vendor could not be reached about TightVNC, so administrators should replace it, and restrict connections to trusted servers until a fixed viewer is deployed.
Sources: NVD and CISA known exploited vulnerabilities catalogue.