CVE-2026-92372: TeamViewer macOS and Linux runs attacker code
CVE-2026-92372, disclosed on October 28, 2026, lets an attacker run code on the TeamViewer client for macOS and Linux by sending crafted screen images during a remote session. According to @IntCyberDigest, the attack happens when the user connects to an attacker-controlled computer. The sources cite no fix; the guidance is to avoid connecting to unknown computers.
What happened
A flaw disclosed on October 28, 2026 in the TeamViewer client for macOS and Linux lets an attacker run code on the machine of the person who starts the remote session. The attack uses crafted screen images sent while connecting to an attacker-controlled computer.
Why it matters
Remote support teams using the client on Mac or Linux can have their own machine hacked when connecting to an unknown computer. The target is the machine of the professional who starts the session, not the remote machine.
What to do
Forbid starting TeamViewer sessions from Mac or Linux to unknown or untrusted computers until a fix exists. Check for an update and apply it when released.
For the technical team
- CVE
- CVE-2026-92372
- Affected
- Cliente TeamViewer para macOS e Linux · TeamViewer client for macOS and Linux. Sources do not state versions.
- Exploitation
- No exploitation reported in the sources. CVE disclosed 2026-10-28; reported by @IntCyberDigest.
- Fix
- Not stated in the sources. Mitigation: do not start sessions to unknown or untrusted computers.
- Vector
- TeamViewer client for macOS and Linux, in receiving screen images during the remote session. The attacker feeds crafted screen images and code runs on the machine that initiates the connection. Condition: connecting to an attacker-controlled computer (reported by @IntCyberDigest).
- More details
- Disclosed 2026-10-28. Sources mention no affected versions, fix, PoC, or in-the-wild exploitation.
Timeline
CVE-2026-92372 disclosed, code execution in the TeamViewer macOS and Linux client via crafted screen images during a remote session.
Sources 1 source
- @IntCyberDigest @IntCyberDigest


