CVE-2026-107612: high-severity vulnerability in GlavSoft TightVNC
World-accessible IPC shared memory with predictable name in TightVNC Server
Published
18Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.8
exploitation probability
—
observed exploitation
nono source reports it
Incorrect permission assignment in GlavSoft TightVNC Server for Windows before 2.8.88 allows a local authenticated user to read or overwrite the inter-process communication handles used between the TightVNC service and its desktop server process. The named shared memory segment in the Global\ namespace that carries the pipe HANDLE values is created with a NULL DACL, and its name is derived from a time-seeded srand(time(0)) value that is predictable to one-second granularity. A low-privileged local process can open the mapping and tamper with the IPC channel of a service running as SYSTEM, potentially leading to disclosure of session data, privilege escalation, or denial of service.
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected products
GlavSoft · TightVNCRelated CVEs — GlavSoft TightVNC
In the same product, most dangerous first.
CVE-2026-107615HIGHDLL search order hijacking via screenhooks libraries in TightVNC ServerEPSS —CVE-2026-107614MEDIUMInteger underflow in TightVNC Server cursor shape trimming leads to out-of-bounds readEPSS —CVE-2026-107613MEDIUMNULL pointer dereference in TightVNC Server Win8ScreenDriver after failed DXGI re-initializationEPSS —CVE-2026-107611HIGHOut-of-bounds read in TightVNC Viewer ZRLE palette decodingEPSS —