# CVE-2026-92376: Local Privilege Escalation via IPC Broker Impersonation in TeamViewer Remote Management Monitoring for Windows


- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 27 Oct 2026
- **Updated:** 27 Oct 2026
- **Also known as:** GHSA-4vr4-8q7m-vjmq

## What is CVE-2026-92376?

CVE-2026-92376 is a high-severity vulnerability in TeamViewer Remote Management - Monitoring, published on 27 Oct 2026. 

### Official description

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.

Weakness: CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2026-92376?


## How do I fix CVE-2026-92376?

No fix has been published for CVE-2026-92376 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92376 being exploited?

There is no known exploitation of CVE-2026-92376 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92376 and fix it if it is affected.

What it is: CVE-2026-92376 is a high-severity vulnerability in TeamViewer Remote Management - Monitoring, published on 27 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-92376 in the wild and no public exploit code.

Affected product: TeamViewer Remote Management - Monitoring. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92376/ (Markdown: https://insights.sbomify.com/CVE-2026-92376/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92376
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92376
- OSV: https://osv.dev/vulnerability/CVE-2026-92376

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92376/
Summaries are generated and may contain mistakes; the official description above is the record.