Full Client: Incorrect Permission Assignment for Critical Resource
CVE-2025-36537 is a high-severity incorrect permission assignment for critical resource vulnerability in Full Client from TeamViewer, with a CVSS 3.1 base score of 7.0 out of 10. It can be exploited with local access to the system by an attacker with a low-privileged account, without any action from a user. The record lists versions 15.67, 14.7.48809, 13.2.36227 as the first without the flaw, so updating Full Client to one of those releases or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.17% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update Full Client to 15.67 or 14.7.48809 or 13.2.36227 or 12.0.259325, whichever matches your release line, or a later version.
- Update Host to 15.67 or 14.7.48809 or 13.2.36227 or 12.0.259325, whichever matches your release line, or a later version.
- Update Full Client (Win7/8) to 15.64.5 or a later version.
- Read the advisory on teamviewer.com for workarounds and exact fixed builds.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| TeamViewer | Full Client | 15.0.0 up to, but not including, 15.67; 14.0.0 up to, but not including, 14.7.48809; 13.0.0 up to, but not including, 13.2.36227; 12.0.0 up to, but not including, 12.0.259325; 11.0.0 up to, but not including, 11.0.259324 | 15.67, 14.7.48809, 13.2.36227, 12.0.259325, 11.0.259324 |
| TeamViewer | Host | 15.0.0 up to, but not including, 15.67; 14.0.0 up to, but not including, 14.7.48809; 13.0.0 up to, but not including, 13.2.36227; 12.0.0 up to, but not including, 12.0.259325; 11.0.0 up to, but not including, 11.0.259324 | 15.67, 14.7.48809, 13.2.36227, 12.0.259325, 11.0.259324 |
| TeamViewer | Full Client (Win7/8) | 15.0.0 up to, but not including, 15.64.5 | 15.64.5 |
| TeamViewer | Host (Win7/8) | 15.0.0 up to, but not including, 15.64.5 | 15.64.5 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- LocalThe attacker needs local access or must trick a user into running something.
- Attack complexity
- HighSuccess depends on conditions outside the attacker's control.
- Privileges required
- LowA basic user account is enough.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- HighData or code can be modified at will.
- Availability
- HighThe component can be taken down completely.
Vector: CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H. Scored by CNA (teamviewer.com).
Official description
Incorrect Permission Assignment for Critical Resource in the TeamViewer Client (Full and Host) of TeamViewer Remote and Tensor prior Version 15.67 on Windows allows a local unprivileged user to trigger arbitrary file deletion with SYSTEM privileges via leveraging the MSI rollback mechanism. The vulnerability only applies to the Remote Management features: Backup, Monitoring, and Patch Management.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Incorrect Permission Assignment for Critical Resource
The product specifies permissions for a security-critical resource in a way that allows that resource to be read or modified by unintended actors.
How developers prevent this class of flaw
- When using a critical resource such as a configuration file, check to see if the resource has insecure permissions (such as being modifiable by any regular user), and generate an error or even exit the software if there is a possibility that the resource could have been modified by an unauthorized party.
- Divide the software into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully defining distinct user groups, privileges, and/or roles. Map these against data, functionality, and the related resources. Then set the permissions accordingly. This will allow you to maintain more fine-grained control over your resources.
- During program startup, explicitly set the default permissions or umask to the most restrictive setting possible. Also set the appropriate permissions during program installation. This will prevent you from inheriting insecure permissions from any user who installs or runs the program.
More Incorrect Permission Assignment for Critical Resource vulnerabilities (CWE-732)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: total).
- Record last changed materially (score, affected products, status or references).
References
Other vulnerabilities in Full Client
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 8.8 High severity
- 8.8 High severity
- 7.3 High severity
Recent Incorrect Permission Assignment for Critical Resource vulnerabilities
- 9.9 Critical severity
- 7.3 High severity
- 8.0 High severity
- 7.1 High severity
- 8.5 High severity
- 9.8 Critical severity
Spotted an error? Tell us.