Skip to main content
CVE-2026-128321VulnerabilityPublished Updated

TightVNC · Tight JPEG Decoding

Affects tightvncSource GCVE Database

0
Compare
Authoritative record:CVE-2026-128321· High 7.8

Not known to be exploited · CVSS 7.8 High.

Data as of 18 Nov 2026, 16:05 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CISA-ADPCVSS 3.17.8
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 13 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
Ubuntu 26.10tightvncpkg:deb/ubuntu/tightvnc?arch=source&distro=stonkingOther threatsAffected
  • =1:1.3.10-10build1
  • =1:1.3.10-11
Fixed in–
Ubuntu 26.04 LTStightvncpkg:deb/ubuntu/tightvnc?arch=source&distro=resoluteOther threatsAffected
  • =1:1.3.10-10
  • =1:1.3.10-10build1
Fixed in–
Ubuntu 24.04 LTStightvncpkg:deb/ubuntu/tightvnc?arch=source&distro=nobleOther threatsAffected
  • 1:1.3.10-7 – 1:1.3.10-8
4 affected builds
Fixed in–
Ubuntu 22.04 LTStightvncpkg:deb/ubuntu/tightvnc?arch=source&distro=jammyOther threatsAffected
  • =1:1.3.10-3
  • =1:1.3.10-5
Fixed in–
Ubuntu 20.04 LTStightvncpkg:deb/ubuntu/tightvnc?arch=source&distro=focalOther threatsAffected
  • =1.3.10-0ubuntu5
Fixed in–
Ubuntu 18.04 LTStightvncpkg:deb/ubuntu/tightvnc?arch=source&distro=bionicOther threatsAffected
  • =1.3.10-0ubuntu3
  • =1.3.10-0ubuntu4
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Users should monitor vendor advisories for updates. Until a fix is available, avoid connecting to untrusted VNC servers to reduce risk.

Description

A heap-based buffer overflow vulnerability exists in the Tight JPEG decoding component of TightVNC and UltraVNC viewers. This occurs because the framebuffer rectangle width, controlled by an attacker, is not properly validated against a fixed-size decoding buffer. A malicious VNC server can exploit this flaw to cause an out-of-bounds heap write when a user connects, leading to application crashes and potential memory corruption.

References

Community reviews

Loading reviews…