CVE-2026-107612

Summary

A local authenticated user can manipulate IPC handles between TightVNC service and desktop server processes due to predictable shared memory names and NULL DACL permissions, potentially leading to privilege escalation or data disclosure.

Exploitability

Exploitation requires a local authenticated account with access to the TightVNC service process, which is moderately difficult but feasible since the vulnerable version allows local users to interact with the service.

Blast radius

The impact could be significant as a low-privileged user could potentially read or overwrite critical IPC handles used by the TightVNC service running as SYSTEM, leading to privilege escalation or denial of service.

Detection

No reliable host or network indicator is derivable from the published description.

Prioritized remediation

Upgrade to TightVNC Server 2.8.88 or later to fix the NULL DACL and predictable shared memory naming issue.

Analysis generated locally by garnet-coder (no data left the box). AI-assisted — verify against primary sources before acting.