GlavSoft TightVNC up to 2.8.87 IPC Channel permission

Summaryinfo

A vulnerability labeled as very critical has been found in GlavSoft TightVNC up to 2.8.87. Affected by this vulnerability is an unknown functionality of the component IPC Channel. The manipulation results in permission. This vulnerability is cataloged as CVE-2026-107612. The attack must be initiated from a local position. There is no exploit available. The affected component should be upgraded.

Detailsinfo

A vulnerability classified as very critical has been found in GlavSoft TightVNC up to 2.8.87. Affected is an unknown part of the component IPC Channel. The manipulation with an unknown input leads to a permission vulnerability. CWE is classifying the issue as CWE-275. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:

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.

The advisory is shared for download at sourceforge.net. This vulnerability is traded as CVE-2026-107612 since 10/08/2026. The exploitability is told to be easy. The attack needs to be approached locally. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 10/08/2026). The MITRE ATT&CK project declares the attack technique as T1222.

Upgrading to version 2.8.88 eliminates this vulnerability.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Vendor

• GlavSoft

Name

• TightVNC

Version

• 2.8.0
• 2.8.1
• 2.8.2
• 2.8.3
• 2.8.4
• 2.8.5
• 2.8.6
• 2.8.7
• 2.8.8
• 2.8.9
• 2.8.10
• 2.8.11
• 2.8.12
• 2.8.13
• 2.8.14
• 2.8.15
• 2.8.16
• 2.8.17
• 2.8.18
• 2.8.19
• 2.8.20
• 2.8.21
• 2.8.22
• 2.8.23
• 2.8.24
• 2.8.25
• 2.8.26
• 2.8.27
• 2.8.28
• 2.8.29
• 2.8.30
• 2.8.31
• 2.8.32
• 2.8.33
• 2.8.34
• 2.8.35
• 2.8.36
• 2.8.37
• 2.8.38
• 2.8.39
• 2.8.40
• 2.8.41
• 2.8.42
• 2.8.43
• 2.8.44
• 2.8.45
• 2.8.46
• 2.8.47
• 2.8.48
• 2.8.49
• 2.8.50
• 2.8.51
• 2.8.52
• 2.8.53
• 2.8.54
• 2.8.55
• 2.8.56
• 2.8.57
• 2.8.58
• 2.8.59
• 2.8.60
• 2.8.61
• 2.8.62
• 2.8.63
• 2.8.64
• 2.8.65
• 2.8.66
• 2.8.67
• 2.8.68
• 2.8.69
• 2.8.70
• 2.8.71
• 2.8.72
• 2.8.73
• 2.8.74
• 2.8.75
• 2.8.76
• 2.8.77
• 2.8.78
• 2.8.79
• 2.8.80
• 2.8.81
• 2.8.82
• 2.8.83
• 2.8.84
• 2.8.85
• 2.8.86
• 2.8.87

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion