TeamViewer has fixed six security vulnerabilities that could let a local user take over a device with SYSTEM privileges in its remote management add-ons and desktop client. The company’s bulletin TV-2026-1012, dated October 27, lists individually which components received fixes and which versions to update to. The vulnerabilities score between 7.3 and 7.8 on the CVSS 3.1 scale. TeamViewer states that at the time of publication it has no information indicating that these vulnerabilities have been exploited in real-world attacks.
Which components are affected
The bulletin covers TeamViewer Full Client and Host, as well as the Monitoring, Advanced Asset Management, and Patch Management add-ons in the Remote Management package. The six vulnerabilities have been assigned CVE-2026-92375, CVE-2026-92376, CVE-2026-92377, CVE-2026-111582, CVE-2026-111583, and CVE-2026-111584. Most of the issues are on the Windows side; however, the Monitoring component is also affected in the macOS and Linux versions.
How the vulnerabilities work
Two vulnerabilities rely directly on inter-process communication (IPC). In CVE-2026-92376, an attacker can impersonate the IPC broker and get the Monitoring service to run code with SYSTEM privileges. CVE-2026-92375 exploits a lack of access control on the same communication channel to allow scripts to run with SYSTEM or root privileges.
There are two separate weaknesses on the Patch Management side. In CVE-2026-92377, a signed executable is fed via a fake IPC response, and then a malicious DLL is loaded from a temporary folder that the user can write to. CVE-2026-111584 uses a race condition during installation to make it possible to replace the service file with another file. The remaining two vulnerabilities involve installation steps: a DLL loading error during Monitoring installation (CVE-2026-111582) and processing of a settings file dropped into the staging folder with SYSTEM privileges during Advanced Asset Management installation (CVE-2026-111583). For these two, user interaction is required for the attack to succeed.
How to update
TeamViewer Full Client and Host users need to move to version 15.83; the download link is on the company’s site. Maintenance builds 15.64.10 for Windows 7 and 8, 14.7.48868 on the 14.7 line, and 13.2.36231 on the 13.2 line have been released. Fixed builds for the same lines are also available for macOS and Linux.
Although Remote Management components update automatically, checking the version is a must: the Monitoring component should be at version 26.10.1 and Patch Management at 26.9.1. For clients on the 14.7 line, the Patch Management fix is 24.12.5. TeamViewer says it distributes these components through automatic updates, but the version number still needs to be verified on managed devices.
Who should prioritize this
Because all the vulnerabilities require a local account, they are not directly remotely exploitable. However, because remote support software runs with SYSTEM privileges, even a small local flaw can open the door to all accounts and corporate connections on that machine. People managing multiple computers, machines accessed by support teams, and fleets with the Remote Management add-on installed should prioritize the update.
Source: TeamViewer Security Bulletin TV-2026-1012 · NVD
Share your experience
Bir sorunun, farklı bir çözümün veya eklemek istediğin bir notun var mı? Giriş yapmadan da yazabilirsin.