Live › vulnerability › CVE-2026-92376
Go to dashboardTeamViewer Remote Management Monitoring for Windows before 26.10.1 has an authentication flaw in its inter-process communication mechanism. A local user with low privileges can impersonate the IPC broker and make the Monitoring service run arbitrary code as NT AUTHORITY\SYSTEM.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-27 16:33 UTC. All times on this page are UTC.
Windows machines running TeamViewer Remote Management Monitoring before are exposed, since any local account with low privileges can escalate to SYSTEM. Teams that manage endpoints through TeamViewer Remote Management should look at those agents. Machines without the Monitoring component installed are not affected.
26.10.1No product ranges from the sources yet.
26.10.1 are in scope26.10.1 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Improper authentication in the inter-process communication (IPC) mechanism of TeamViewer Remote Management Monitoring for Windows prior to version 26.10.1 allows a local authenticated attacker with low privileges to impersonate the IPC broker and cause the Monitoring service to execute arbitrary code with NT AUTHORITY\SYSTEM privileges, resulting in local privilege escalation.
This page as .md · .json · in your agent: get_signal("CVE-2026-92376")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.