CVE-2026-107612 World-accessible IPC shared memory with predictable name in TightVNC Server

High 7.8 Published Updated

A local attacker can read or modify IPC shared memory in TightVNC Server due to weak permissions and predictable naming, potentially exposing session data or escalating privileges.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Local or same network only
Victim action needed
Not needed
Fix
None listed

What is CVE-2026-107612?

CVE-2026-107612 is a high-severity vulnerability in GlavSoft TightVNC, published on 8 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.

Official 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.

Weakness: CWE-732, CWE-338

Which versions are affected by CVE-2026-107612?

How do I fix CVE-2026-107612?

No fix has been published for CVE-2026-107612 yet. Limit exposure of the affected software until one is available.

Is CVE-2026-107612 being exploited?

There is no known exploitation of CVE-2026-107612 in the wild and no public exploit code.

Sources

Also known as GHSA-95xq-4x4f-23hr.

Is CVE-2026-107612 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free