Monday 16 November
Global

Your region, kept on this device.

TightVNC and UltraVNC Viewer heap overflow can be triggered by a malicious VNC server

Severity
High
Exploited
Not known
Sources
1

A heap-based buffer overflow in the Tight JPEG decoding of Windows Viewer 1.3.10 and affected 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.

For IT people · Written by AI from 1 source · Wrong?

What to do

  1. Upgrade UltraVNC Viewer to version 1.8.3.1 or another release containing the 1.8.2.8 fix.
  2. Replace TightVNC Windows Viewer 1.3.10 with a maintained viewer or an alternative confirmed to address the flaw, as the vendor could not be reached.
  3. Restrict VNC viewer connections to trusted servers until a corrected viewer is deployed.

Written by AI from the sources, checked against them

Vulnerabilities

Full story timeline · 2 updates

  1. Fri 13 NovemberVU#644655: TightVNC and UltraVNC Viewer contains a heap-based buffer overflowCERT/CC Vulnerability Notes
  2. CVE-2026-128321 publishedNVD

Who reported · 1 outlet

CERT/CC Vulnerability Notes

Who and what is in it

Report a problem