A malicious or compromised host can crash the viewer that connects to it or, depending on the platform, potentially run code there. It affects the Full Client, Portable and Android app before 15.83, and 15.83 fixes it.
What it allows
The CVE record says a malicious remote host can crash the TeamViewer viewer or, depending on the platform, potentially run code "with the privileges of the viewer process." The viewer is the side that opens a remote-control session; at a support desk, that is the technician. Exploitation needs the user to connect to a host that the attacker controls or has compromised.
TeamViewer, acting as CNA, scores the flaw 8.8 High in CVSS 3.1. Neither the CVE record nor NVD carries a CVSS 4.0 score. The record credits Omri Dar with finding it, and his Remedio write-up explains the bug.
How the Overflow Works
When a session starts, the host tells the viewer the size of the screen it will stream. Remedio says the viewer uses that width, height and colour depth to size a pixel buffer, with no upper limit on the numbers.
The size is computed in 32-bit arithmetic, so large values wrap around to a small allocation. The decoder still checks each screen update against the declared size, not the real one. One full-screen update then writes far past the buffer on the heap.
Remedio says a host can force this path by refusing the hardware video codecs, which leaves the viewer on the bitmap buffer. The attacker also picks the dimensions, and with them the size of the undersized buffer.
From Crash to Code Execution
On Windows, Remedio says it bypassed Control Flow Guard and DEP and ran a program of its choosing on the viewer. It tested viewer 15.80.6.0 and says the vulnerable code was still present in 15.82.6.0.
In its demo, a hook on the host placed the corrupting bytes and stood in for the heap grooming step. Remedio says the bug is reachable in the default configuration once a session is accepted.
Who Is Most at Risk?
The risk sits with whoever connects out, not with the machine being supported. That is the help desk or managed service provider whose technicians open sessions to customer machines many times a day.
A customer machine that is already compromised could be used against the technician. That inference is ours, drawn from the record's condition of a compromised host. Our TeamViewer update steps for support desks cover what to do before the next session.
The same bulletin fixes two other client flaws. CVE-2026-92372, also 8.8 High, is an out-of-bounds write in the screen-image decoder of the Linux and macOS Full Client. Its record says a crafted session recording (.tvs) can trigger it too. CVE-2026-92374 is a local privilege escalation in the macOS Full Client and Host.
What Our Checks Showed
These are the public signals we checked on 31 October 2026.
- CISA KEVNot seenNot listed in catalog version 2026.10.3031 Oct
- Vendor statementNot seenTeamViewer was not aware of active exploitation when it published the bulletin27 Oct
- Researcher demoYesRemedio says it ran its own program on a Windows viewer, using a host-side hook in the demo29 Oct
- Alerts on XYes39 public posts from 27 to 31 October name the CVE, including Remedio's own31 Oct
- Brandefense BlackholeYesSix Telegram news-channel posts from 27 to 31 October repeat the bulletin or news reports31 Oct
The Blackhole posts are reposts in Telegram news channels and add nothing beyond the bulletin and Remedio's write-up. Remedio's account announced the research on X on 29 October.
Another recent heap overflow driven by crafted image data is the Pillow FlashPix heap buffer overflow. Our remote code execution glossary entry explains what an attacker can do with that kind of access.
Integer overflows in file and image parsers keep recurring across products. CVE-2026-123614 is a 32-bit overflow in imgproxy's ICO loader that undersizes a heap buffer, fixed in imgproxy 4.0.16.
Who is affected
The TeamViewer bulletin TV-2026-1011 lists the Full Client, including the Portable version, before 15.83 on Windows, Linux and macOS. It also lists the Android Remote Control app before 15.83 and three legacy branches.
- Affected
- Fixed
The CVE record also lists Portable on the 15.64 legacy branch for Windows 7 and 8, fixed in 15.64.10. The bulletin's legacy table names only Full Client and Host builds for that branch.
TeamViewer Host is not in the affected list for CVE-2026-111585, which targets the viewer. The bulletin fixes Host in 15.83 for the macOS flaw CVE-2026-92374, so update Host as well.
The bulletin's only mitigation is the update: "15.83 or the latest version available." Our patch management glossary entry covers how to track a fix across many machines.
Timeline
-
14 Aug 2026
Remedio says it reported the flaw to TeamViewer Product Security.
-
16 Oct 2026
TeamViewer, as CNA, reserves CVE-2026-111585.
-
22 Oct 2026
Remedio says TeamViewer accepted the finding at CVSS 8.8 High.
-
27 Oct 2026
TeamViewer issues bulletin TV-2026-1011, and the CVE record goes public. Remedio says 15.83 shipped the same day.
-
28 Oct 2026
TeamViewer updates the bulletin.
-
29 Oct 2026
Remedio publishes its write-up by Omri Dar.
-
31 Oct 2026
The CVE is not in CISA KEV, catalog version 2026.10.30, and NVD lists it as awaiting analysis.
What to do
-
Update Every Viewer to 15.83
Update the Full Client, Portable copies and the Android Remote Control app to 15.83. Legacy branches take 15.64.10, 14.7.48868 or the 13.2 build for their platform.
-
Start With Support Technicians
The viewer is the target, so update the machines that open sessions to other computers first: help desk laptops, jump hosts and the machines of managed service provider staff.
-
Check for the Update by Hand
TeamViewer says auto-update checks weekly by default. Use Help, then Check for new version, rather than waiting for the next check.
-
Enforce Updates Through a Policy
On Business, Premium, Corporate and Tensor licences, an update policy can check for and install new versions on full clients and Host clients, and can be enforced.
-
Avoid Untrusted Hosts Until Patched
Our advice, not a vendor statement: until a viewer runs 15.83, do not use it to connect to a host you have reason to distrust.
What Brandefense can do
- Watch your stack for exploited flaws
Name the vendors and products you run, and Brandefense alerts you when a CVE in them is exploited.
- See CVE-2026-111585 in Brandefense Atlas
The Atlas record of CVE-2026-111585: severity, exploitation status and the sources behind it.
- Vulnerability intelligence platform
Brandefense Vulnerability Intelligence follows which vulnerabilities attackers are using, so your team can patch what is under attack first.
Frequently Asked Questions
Is CVE-2026-111585 exploited?
CISA's KEV catalog did not list it on 31 October 2026. TeamViewer said it was not aware of active exploitation when it published the bulletin. Remedio showed code execution in its own demo.
Who is at risk from CVE-2026-111585?
The person who connects out: the viewer, usually a support technician. The attack needs a remote-control session to a host that the attacker controls or has compromised.
Is TeamViewer Host affected?
The CVE-2026-111585 record does not list Host. The same bulletin fixes Host in 15.83 for the macOS flaw CVE-2026-92374, so update it too.
Which version fixes CVE-2026-111585?
TeamViewer 15.83 for the Full Client, Portable and the Android app. Legacy branches are fixed in 15.64.10, 14.7.48868, 13.2.36231 on Windows, 13.2.154008 on Linux and 13.2.154007 on macOS.
Sources
- TV-2026-1011: Security Update for Vulnerabilities in TeamViewer ClientsTeamViewer
- CVE-2026-111585 RecordCVE Program / TeamViewer CNA
- CVE-2026-111585NVD
- Remote Code Execution in TeamViewer (CVE-2026-111585)Remedio (Omri Dar)
- CVE-2026-92372 RecordCVE Program / TeamViewer CNA
- Update TeamViewerTeamViewer Knowledge Base
- Update TeamViewer via policyTeamViewer Knowledge Base
- Known Exploited Vulnerabilities CatalogCISA