CVE-2026-92370 — Remote Session Access Control Bypass Leading to Remote Code Execution
An improper access control vulnerability in TeamViewer Full Client, Host, and related affected modules on Windows, Linux, and macOS allows an authenticated remote attacker to bypass user-configured permission settings during session establishment. By modifying access control parameters for restricted features, an attacker can perform actions that were explicitly denied by the victim's configuration. This may result in unauthorized actions and potentially lead to remote code execution on the target system.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 0.4% (30-day exploitation probability)+4
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Teamviewer Full Client, Teamviewer Host).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Exploitation requires user interaction: tighten email/web filtering and warn affected users.
- Search available logs for exploit probes matching the vulnerability class (access control), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Teamviewer | Full Client | ≥ 15.0 and < 15.82≥ 15.64.0 (Legacy Windows 7 & 8) and < 15.64.8 (Legacy Windows 7 & 8)≥ 14.7.0 (Windows) and < 14.7.48855 (Windows)≥ 13.2.0 (Windows) and < 13.2.36230 (Windows)≥ 14.7.0 (Linux) and < 14.7.48855 (Linux)≥ 13.2.0 (Linux) and < 13.2.153995 (Linux)≥ 14.7.0 (MacOS) and < 14.7.48855 (MacOS)≥ 13.2.0 (MacOS) and < 13.2.153994 (MacOS) | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Teamviewer | Host | ≥ 15.0 and < 15.82≥ 15.64.0 (Legacy Windows 7 & 8) and < 15.64.8 (Legacy Windows 7 & 8)≥ 14.7.0 (Windows) and < 14.7.48855 (Windows)≥ 13.2.0 (Windows) and < 13.2.36230 (Windows)≥ 14.7.0 (Linux) and < 14.7.48855 (Linux)≥ 13.2.0 (Linux) and < 13.2.153995 (Linux)≥ 14.7.0 (MacOS) and < 14.7.48855 (MacOS)≥ 13.2.0 (MacOS) and < 13.2.153994 (MacOS) | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.8 | CVSS 3.1 | High | 2.8 | 5.9 | psirt@teamviewer.com via NIST National Vulnerability Database |
| 8.8 | CVSS 3.1 | High | — | — | TV via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: psirt@teamviewer.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Audit administrative actions and access to resources outside each user’s normal pattern.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · teamviewer/full client, teamviewer/host
- SSVC assessment updated
- Record published
- CVSS changed · 8.8
- Source status changed · → Deferred
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 15, 2026 – Oct 15, 2026
References
1 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-92371 Local Privilege Escalation via Improper Link Resolution in Cloud Session Recording 16d
- High CVE-2026-92368 Heap-Based Buffer Overflow in TeamViewer Session Recording Playback Leads to Remote Code Execution 16d
- High CVE-2026-92369 Time-of-check Time-of-use (TOCTOU) Race Condition in TeamViewer Windows Installer Rollback Mechanism Leads to Local Privilege Escalation 16d
- High CVE-2026-19743 Improper Limitation of a Pathname to a Restricted Directory (Path Traversal) in TeamViewer Desktop Clients 16d
- High CVE-2026-19042 Command Injection in TeamViewer Desktop Client for Linux through Chat Link Handling Aug 26, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-92370 is "Remote Session Access Control Bypass Leading to Remote Code Execution", rated High. It affects Full Client (Teamviewer); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.8 describes technical severity. EPSS 0.38% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.