CVE-2026-107612
World-accessible IPC shared memory with predictable name in TightVNC Server
- High 7.8
Description
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.
Key facts
- Published
- 8 Oct 2026
- Last changed
- 8 Oct 2026
- Assigned by
- securin
- EPSS
- 0.104% likely to be exploited in the next 30 days, higher than 1.036% of CVEs (scores for 17 Nov 2026)
- SSVC (CISA)
- Exploitation: none; Automatable: no; Technical impact: total
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 7.8CVSS 3.1, Highfrom the CNA (securin)
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
What to do
- Upgrade TightVNC for Windows to version 2.8.88 or later.CNA solution statement
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
CAPEC-122 Privilege Abuse (CNA impact statement)
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| GlavSoft | TightVNC |
|
Timeline
- 30 May 2026 Reported to GlavSoft
- 2 Jun 2026 Vendor acknowledged
- 19 Jun 2026 TightVNC 2.8.88 released with fix
- 8 Oct 2026 Published