TeamViewer Full Client/Host up to 15.81.5 Installer Staging Directory access control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 1.91 |
Summary
A vulnerability has been found in TeamViewer Full Client and Host and classified as very critical. This issue affects some unknown processing of the component Installer Staging Directory. The manipulation leads to access control. This vulnerability is traded as CVE-2026-111583. An attack has to be approached locally. There is no exploit available. The affected component should be upgraded.
Details
A vulnerability was found in TeamViewer Full Client and Host. It has been rated as very critical. This issue affects an unknown part of the component Installer Staging Directory. The manipulation with an unknown input leads to a access control vulnerability. Using CWE to declare the problem leads to CWE-284. The product does not restrict or incorrectly restricts access to a resource from an unauthorized actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
Improper access control in the installer staging directory used by TeamViewer Full Client and Host prior to version 15.82 for Windows during installation of Advanced Asset Management allows a local authenticated user with low privileges to execute arbitrary commands as SYSTEM. An attacker can place a crafted installer options file that is processed by the Advanced Asset Management installer during service activation.
The advisory is shared at teamviewer.com. The identification of this vulnerability is CVE-2026-111583 since 10/16/2026. The exploitation is known to be easy. An attack has to be approached locally. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/27/2026). MITRE ATT&CK project uses the attack technique T1068 for this issue.
Upgrading to version 15.82 eliminates this vulnerability.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
- 13.2.36230
- 13.2.36231
- 13.2.153978
- 13.2.153994
- 13.2.153995
- 13.2.154007
- 14.7.48854
- 14.7.48855
- 14.7.48867
- 14.7.48868
- 14.7.488837
- 14.7.488838
- 15.69
- 15.70
- 15.81
- 15.81.4
- 15.81.5
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.6
VulDB Base Score: 8.2
VulDB Temp Score: 7.8
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 7.3
CNA Vector: 🔒
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: Access controlCWE: CWE-284 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: Partially
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: Full Client/Host 15.82
Timeline
10/16/2026 CVE reserved10/27/2026 Advisory disclosed
10/27/2026 VulDB entry created
10/27/2026 VulDB entry last update
Sources
Advisory: teamviewer.comStatus: Confirmed
CVE: CVE-2026-111583 (🔒)
GCVE (CVE): GCVE-0-2026-111583
GCVE (VulDB): GCVE-100-427409
Entry
Created: 10/27/2026 16:36Changes: 10/27/2026 16:36 (63)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.