CERT/CC has published advisory VU#644655 describing a heap buffer overflow vulnerability (CVE-2026-128321) in the Tight JPEG decoding component of TightVNC Windows Viewer version 1.3.10 and affected versions of UltraVNC Windows Viewer. An attacker controlling a VNC server can cause memory corruption on the client side by sending a specially crafted screen update. Denial of service has been confirmed; arbitrary code execution is described as possible, but was not demonstrated during testing. UltraVNC has released a fix, whereas there is no coordinated patch for TightVNC 1.3.10 — CERT/CC recommends replacing this viewer.
Technical details of the vulnerability
The vulnerability is located in the DecompressJpegRect() function, which is responsible for decoding JPEG data as part of screen updates over the RFB (Remote Framebuffer) protocol. The function allocates a heap buffer sized for a maximum line width of 8,192 pixels, but when converting pixel data it uses the rectangle width received from the server without properly checking that the result fits into the allocated memory.
According to the CERT/CC advisory, during testing the out-of-bounds write began at a rectangle width of 8,257 pixels, in an allocation that included an extra 256-byte margin. It should be noted that this threshold is specific to the particular test configuration and is not a universal boundary for exploitability.
The key feature of the attack vector is that the VNC server is the trust boundary. A malicious server can declare a sufficiently large framebuffer, so simply checking that the rectangle fits within the declared dimensions does not in itself prevent the overflow. Moreover, authentication and transport encryption do not protect against exploitation if a malicious server participates in the session — these mechanisms verify the parties’ identities but do not limit the content of transmitted data.
Affected products
- TightVNC Windows Viewer version 1.3.10
- UltraVNC Windows Viewers — affected versions; the CERT/CC advisory does not specify the full range of vulnerable UltraVNC versions
The materials reviewed do not contain information about active exploitation of the vulnerability in real-world attacks. A CVSS assessment is also not provided.
Differences in patch status
The patch situation is fundamentally different for the two affected products, and administrators need to determine exactly which viewer is used in their infrastructure before applying the recommendations.
UltraVNC fixed the vulnerability in version 1.8.2.8. CERT/CC recommends updating to the current supported release, for example version 1.8.3.1. According to the commit in the UltraVNC repository, the fix changes the buffer allocation logic: the size is now calculated based on the actual rectangle width rather than a hard-coded value, and a check has been added for non-positive or out-of-range dimensions.
TightVNC presents a more complicated situation. According to the CERT/CC advisory, the coordination center was unable to contact the TightVNC developers to coordinate the release of a patch for the affected 1.3.10 Windows Viewer version. CERT/CC’s recommendation is to replace this viewer with a supported version or an alternative solution for which remediation of the vulnerability has been confirmed. The material reviewed does not establish whether TightVNC has released an independent fix outside the coordinated process.
Impact assessment
The vulnerability affects scenarios in which a user connects with a VNC viewer to a server controlled by an attacker or to a compromised server. This may be relevant for:
- Support environments where specialists connect to client servers
- Reverse VNC scenarios, where the server initiates a connection to the viewer
- Any situations where a VNC server may be compromised by a third party
The confirmed impact is abnormal termination of the viewer and interruption of the remote session. According to CERT/CC, heap memory corruption may allow arbitrary code execution with the privileges of the user running the viewer; however, testing only confirmed denial of service.
Recommendations
- Determine which product is in use. Check which VNC viewer is deployed — TightVNC or UltraVNC — and its version.
- For UltraVNC: update to version 1.8.3.1 or later, which includes the fix first introduced in 1.8.2.8.
- For TightVNC 1.3.10: replace the viewer with a supported alternative for which the absence of this vulnerability has been confirmed.
- Temporary measure: until a fixed viewer is deployed, restrict connections to trusted VNC servers only. This measure reduces risk but does not eliminate it entirely — a compromised trusted server can still deliver a malicious update.
Organizations using TightVNC Windows Viewer 1.3.10 should prioritize its replacement, since there is no coordinated fix from the developer and the temporary measure of restricting connections does not provide full protection. UltraVNC users only need to update to the current version — the fix is documented and available. Additional information is available in the NVD entry for CVE-2026-128321.












