# CVE-2026-111584: Local Privilege Escalation via Race Condition in TeamViewer Patch Management for Windows


- **Severity:** High 7.3 (`CVSS:3.1/AV:L/AC:L/PR:L/UI:R/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-h5jh-rr9v-jv3h

## What is CVE-2026-111584?

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

### Official description

A race condition in the installation
process of TeamViewer Remote Management - Patch Management for Windows prior to
version 26.9.1 allows a local authenticated attacker with low privileges to
execute arbitrary code with elevated privileges by replacing the service
executable in an insufficiently protected temporary directory during Patch
Management activation.

Weakness: CWE-269 (Improper Privilege Management)

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


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

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

## Is CVE-2026-111584 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected product: TeamViewer Remote - Patch Management. 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-111584/ (Markdown: https://insights.sbomify.com/CVE-2026-111584/index.md)
```

## Sources

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

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