TeamViewer fixes a flaw where the computer you connect to can attack yours
TeamViewer's bulletin TV-2026-1011 (27 Oct 2026) fixes CVE-2026-111585, rated 8.8: a malicious computer you start a remote-control session with could crash your client or possibly run code. No exploitation known. Who is affected and what to update.
How urgent
Plan this week
Who is affected
People who use the TeamViewer client to connect to other computers (Full Client, Portable, or the Android Remote Control app) on a version before 15.83. Older maintenance lines 15.64, 14.7 and 13.2 also have fixed builds. This does not concern you if you only let others connect to you or do not use TeamViewer
What to do
Update the TeamViewer client to 15.83 (or the fixed build of your older line), and only start remote-control sessions with computers you trust. TeamViewer says it is not aware of exploitation in the wild
Published 2 Nov 2026 · Sources last checked 2 Nov 2026No. 32 / 87
What happened
TeamViewer published security bulletin TV-2026-1011 on 27 October 2026 (updated on 28 October). One of its flaws is CVE-2026-111585, rated 8.8 out of 10 (high). It is an integer overflow in the part of the client that decompresses the screen image during a remote-control session. It can lead to a heap-based buffer overflow, a memory error.
According to the bulletin, a malicious remote computer could crash the client or, depending on the platform, possibly run code with the privileges of the viewer process. In plain terms: the risk is reversed. Normally you worry about who connects to you; here the danger is the machine you connect to.
What it takes
The bulletin says no privileges are needed, but a user has to start a remote-control session with a computer controlled by the attacker, or with one that has been compromised. If you never open sessions to computers you do not trust, the exposure is small.
TeamViewer says that, at the time of publication, it was not aware of any active exploitation in the wild. CISA's exploited-flaws list does not include this CVECVE A public ID number, like CVE-2026-12345, given to one specific security flaw so everyone can talk about the same bug. Tap again to open the glossary as far as we checked.
Who is affected
- TeamViewer Full Client (including Portable) before 15.83 on Windows, Linux and macOS.
- TeamViewer Remote Control for Android before 15.83.
- Older maintenance lines: 15.64 (Windows), 14.7 and 13.2 (Windows, Linux, macOS).
Fixed versions listed by TeamViewer: 15.83 (Full Client, Host, Portable and the Android app), 15.64.10 (Windows 7/8), 14.7.48868 (Windows, Linux, macOS), 13.2.36231 (Windows), 13.2.154008 (Linux) and 13.2.154007 (macOS).
What to do
This is our reading of the vendor's bulletin; use it for the details.
- Check your TeamViewer version (Help, About) on every computer you use to connect to others, including laptops and phones.
- Update to 15.83, or to the fixed build of your older line from the list above.
- Connect only to computers you trust. This is our advice, not TeamViewer's: treat a session with an unknown machine as risky until you are patched.
- If you manage a team, push the update through whatever tool you use to manage software, and ask people to avoid sessions with unknown hosts until it is done.
If you build with AI tools
Our advice, not from the bulletin: if you use TeamViewer to reach a server or a rented GPU machine, keep that client updated. A viewer that is compromised sits on the computer where your keys and logins usually live.
What we could not confirm
We read TeamViewer's own bulletin. We did not read the NVD entry, and we did not read the press reports that describe the flaw; the exact conditions and how likely code execution is on each platform come only from the bulletin's wording ("possibly", "depending on the platform"). We have not tested the flaw or the fix.
Comments
No account needed. Add a nickname if you like, or leave it empty to comment anonymously. Comments are reviewed before they appear. Links are not allowed.
We store your comment, your nickname and a scrambled form of your connection that we use only to limit spam. We do not store your IP address or set cookies. Cloudflare Turnstile checks that you are not a bot.
Sources and verification
We use primary sources first and say when we rely on a news report. Dates are the day we last checked each source.
Spotted a mistake? Email [email protected] and we will correct it and note the change.