GlavSoft TightVNC up to 2.8.87 Win8ScreenDriver null pointer dereference
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.5 | $0-$5k | 1.30+ |
Summary
A vulnerability identified as problematic has been detected in GlavSoft TightVNC up to 2.8.87. Affected is the function applyNewScreenProperties/executeDetection/getScreenBuffer/grabFb/getScreenPropertiesChanged/getCursorPosition of the component Win8ScreenDriver. The manipulation leads to null pointer dereference.
This vulnerability is listed as CVE-2026-107613. The attack may be initiated remotely. There is no available exploit.
You should upgrade the affected component.
Details
A vulnerability was found in GlavSoft TightVNC up to 2.8.87. It has been rated as problematic. This issue affects the function applyNewScreenProperties/executeDetection/getScreenBuffer/grabFb/getScreenPropertiesChanged/getCursorPosition of the component Win8ScreenDriver. The manipulation with an unknown input leads to a null pointer dereference vulnerability. Using CWE to declare the problem leads to CWE-476. A NULL pointer dereference occurs when the application dereferences a pointer that it expects to be valid, but is NULL, typically causing a crash or exit. Impacted is availability. The summary by CVE is:
A NULL pointer dereference vulnerability in the Win8ScreenDriver component of GlavSoft TightVNC Server for Windows before 2.8.88 allows an attacker to crash the server, causing a denial of service. When re-initialization of the DXGI Desktop Duplication driver fails in applyNewScreenProperties() (for example after a GPU reset, display hot-plug or session change), m_drvImpl is left NULL and is subsequently dereferenced without a check by executeDetection(), getScreenBuffer(), grabFb(), getScreenPropertiesChanged() and getCursorPosition().
It is possible to read the advisory at sourceforge.net. The identification of this vulnerability is CVE-2026-107613 since 10/08/2026. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. Technical details of the vulnerability are known, but there is no available exploit.
Upgrading to version 2.8.88 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Vendor
Name
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.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.6VulDB Meta Temp Score: 5.5
VulDB Base Score: 5.3
VulDB Temp Score: 5.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 5.9
CNA Vector (securin): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Null pointer dereferenceCWE: CWE-476 / CWE-404
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: TightVNC 2.8.88
Timeline
10/08/2026 Advisory disclosed10/08/2026 CVE reserved
10/08/2026 VulDB entry created
10/08/2026 VulDB entry last update
Sources
Advisory: sourceforge.netStatus: Confirmed
CVE: CVE-2026-107613 (🔒)
GCVE (CVE): GCVE-0-2026-107613
GCVE (VulDB): GCVE-100-415403
Entry
Created: 10/08/2026 16:15Changes: 10/08/2026 16:15 (64)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.