# CVE-2026-92372: Out-of-bounds Write in TeamViewer Full Client for Linux and macOS Allows Remote Code Execution


- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/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-2p63-5vwr-rhf8

## What is CVE-2026-92372?

CVE-2026-92372 is a high-severity vulnerability in TeamViewer Full Client, published on 27 Oct 2026. 

### Official description

An out-of-bounds write vulnerability in the
screen-image decoder of TeamViewer Full Client for Linux and macOS prior to
version 15.83 allows a remote attacker to execute arbitrary code by supplying
crafted screen-image data during a remote-control session. The vulnerability
can also be exploited by persuading a user to open a specially crafted
TeamViewer session recording (.tvs). Missing destination bounds checking in the
decoder allows crafted screen-image data to cause an out-of-bounds write to the
image buffer. Exploitation requires user interaction.

Weakness: CWE-123 (Write-what-where Condition)

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


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

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

## Is CVE-2026-92372 being exploited?

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

## Fix prompt for AI coding agents

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

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

Affected product: TeamViewer Full Client. 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-92372/ (Markdown: https://insights.sbomify.com/CVE-2026-92372/index.md)
```

## Sources

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

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