The news
TeamViewer, WatchGuard and MikroTik products all received fixes or warnings for serious flaws on September 29. The most severe TeamViewer vulnerability lets a remote attacker bypass session permissions. None of the flaws was known to be exploited when disclosed, giving defenders a short head start.
TeamViewer's security bulletin TV-2026-1010 lists five flaws in its Full Client and Host software for Windows, Linux and macOS. The worst, CVE-2026-92370, is rated 8.8 out of 10: an improper access control flaw that lets an authenticated remote attacker bypass the permissions a user set for incoming sessions, which could potentially lead to code execution. The other four, rated 7.0 to 7.8, mostly let local attackers escalate privileges or run code; one requires a user to open a crafted session recording file. Version 15.82 fixes them, and TeamViewer said it was not aware of any public disclosure or active exploitation. BleepingComputer reported that TeamViewer strongly recommends all users update as soon as possible.
WatchGuard's most serious issue, CVE-2026-86131, is rated 9.2 and affects Firebox appliances running Fireware OS with a BOVPN over TLS client configuration, a type of site-to-site VPN link. According to WatchGuard's advisory, an attacker who controls the remote VPN server can run commands as root on the connecting Firebox. Fixed versions are Fireware OS 2026.3.2, 2026.2.3, 12.12.3 and 12.5.21. SecurityWeek reported the same release fixed 13 high-severity flaws and one medium-severity issue, including some that can be exploited without authentication. WatchGuard said it was not aware of exploitation in the wild.
The most dangerous of the three on paper is in MikroTik's RouterOS, router software that CISA says is deployed worldwide. A CISA advisory released September 29 describes CVE-2026-84411, rated 9.8 under CVSS 3.1, as an integer underflow in the web management service that is reachable before login. A single crafted request could let an unauthenticated attacker run code as root or crash the device. RouterOS versions before 7.24 are affected, and CISA recommends updating to 7.24 or later. An anonymous researcher reported the flaw, and CISA said no known public exploitation had been reported to it.
Remote-access tools and edge devices are frequent targets. BleepingComputer noted that TeamViewer's software has previously been abused by ransomware gangs to break into networks, and Google Threat Intelligence Group reported on September 30 that 14% of vulnerabilities exploited from January to August 2026 affected edge and security appliances.
The numbers
- MikroTik CVE-2026-84411 score (CVSS 3.1)
- 9.8
- WatchGuard CVE-2026-86131 score (CVSS 4.0)
- 9.2
- TeamViewer CVE-2026-92370 score
- 8.8
- WatchGuard Fireware OS flaws fixed
- 15
- TeamViewer fixed version
- 15.82
- MikroTik fixed version
- RouterOS 7.24 or later
Why CEOs should care
For CISOs, this is a clear order of work for the week. Start with MikroTik: any router whose web management interface can be reached from the internet or an untrusted network is the highest risk, because no password is needed and one request is enough. Update to RouterOS 7.24 or later, and restrict the management interface to a trusted admin network. Next, push TeamViewer 15.82 to every managed machine, and hunt for unmanaged copies installed by staff or contractors; a tool that grants remote control is only as safe as its oldest install.
WatchGuard deserves a careful read rather than panic. The 9.2-rated bug requires the Firebox to connect to a VPN server the attacker controls, so first check whether any BOVPN over TLS client links are configured, and to whom. But the same release fixes 13 high-severity flaws, some reachable without login, so schedule the upgrade regardless.
For CIOs and boards, ask two questions. Do our managed service providers use TeamViewer or MikroTik gear to reach our systems, and have they confirmed the updates? And how long does it take us to patch internet-facing devices after a fix ships? With no exploitation reported yet, the gap between the fix and the first attacks is the window that matters.
The bigger picture
Fixes published together give attackers a map, too. Google's threat researchers wrote that attackers may be using AI tools to compare patched and unpatched software and turn fixes into working attacks faster. Firewalls, VPNs and remote-access tools sit at the edge of the network and often hold high privileges, which is why they are worth the attention.
What’s next
Watch CISA's Known Exploited Vulnerabilities catalog for any of these three CVEs. A listing would mean confirmed attacks and, for federal civilian agencies, a fixed patch deadline. Also watch for public proof-of-concept code, which often comes before widespread scanning.
What “Fact-checked” means
Fact-checking means testing a story’s facts against the evidence before it is published. This story went through at least two separate checks before this version was published.
- What we checked
- Its names, figures, dates, job titles, quotes and who said what were checked against the story’s sources, including its main source where it could be opened. The headline was checked for accuracy and overstatement.
- How
- A first check reviewed the whole story. If it passed, a second, skeptical check went back to the sources to look for mistakes in the most important facts. If a check flagged the story, it was edited to fix the problems found, and a separate re-check then reviewed the whole story again.
- Who
- The checks are made by our newsroom, as steps kept separate from the writing, under rules set by our editor, Hussein Mukhtar. A story the checks still flag is held for the editor, who decides whether it is fixed, published or dropped.
- If something is wrong
- “Fact-checked” does not mean error-free. If a material error is found after publication, we correct the story and add a note saying what changed. Report an error







