Read the docs

Heap buffer overflow in TightVNC and UltraVNC Tight JPEG decoding

Priority LOW 22Published · Updated

Key facts

Attack vector
—
Privileges required
—
User interaction
—
Attack complexity
—
Impact type
—
Confidentiality · integrity · availability
—
Fix status
No fix listed

No CVSS vector from any source. Fix status from CNA.

Summary

UltraVNC versions from 1.8.2.4 through 1.8.2.6 and TightVNC 1.3.10 are affected. Tight JPEG decoding in the viewers does not validate an attacker-controlled framebuffer rectangle width against a fixed-size decoding buffer, causing a heap-based buffer overflow. A malicious VNC server can trigger an out-of-bounds heap write when a user connects, crashing the application and potentially causing other memory corruption.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Description from the CNA

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.

Why it matters now

EPSS 0.00203 10th percentileScored 2026-11-16
Fix No fix listed No fixed version in the sources yet

SSVC decision points

Not available: CISA has not published SSVC decision points for this record.

Affected products

VendorProductAffected versionsFixed inStatusSource
UltraVNCUltraVNC1.8.2.4 – 1.8.2.6—No fix listedCNA
Glavsoft (TightVNC)TightVNC1.3.10 – 1.3.10—No fix listedCNA
  • UltraVNC VendorUltraVNC Affected 1.8.2.4 – 1.8.2.6 Fixed in — No fix listed CNA
  • TightVNC VendorGlavsoft (TightVNC) Affected 1.3.10 – 1.3.10 Fixed in — No fix listed CNA

CPE names Threatist (inferred) · 1

Inferred from how NVD named this product before; not given by a source.

CPEVersionsRoleVendor
cpe:2.3:a:uvnc:ultravnc:*:*:*:*:*:*:*:*——uvnc
  • cpe:2.3:a:uvnc:ultravnc:*:*:*:*:*:*:*:* Versions — — ·uvnc

Remediation

The sources list no fixed version for UltraVNC. The sources list no fixed version for TightVNC.

Written with Claude Haiku 5.5 from the sources below · 2026-11-13

Timeline

  1. 2026-11-13 Threatist record created from CVE-2026-128321
  2. 2026-11-13 Alias added: GHSA-2v2r-xq5w-26rm

References

  • TI-2006-01599 Multiple buffer overflows in (a) UltraVNC (aka Ultr@VNC) 1.0.1 and earlier and (b)… CVSS 2.0HIGH 9.0
  • TI-2008-00582 Stack-based buffer overflow in the ClientConnection::NegotiateProtocolVersion function in… CVSS 2.0HIGH 9.3
  • TI-2009-00368 Multiple integer signedness errors in (1) UltraVNC 1.0.2 and 1.0.5 and (2) TightVnc 1.3.9… CVSS 2.0HIGH 10.0
  • TI-2019-05934 Heap-based buffer overflow in UltraVNC CVSS 3.1CRITICAL 9.8
  • TI-2019-05930 Heap-based buffer overflow in UltraVNC CVSS 3.1CRITICAL 9.8
  • TI-2008-04755 Multiple stack-based buffer overflows in multiple functions in vncviewer/FileTransfer.cpp… CVSS 2.0HIGH 9.3
See all 14 →

Sources