GL.iNet says attackers exploited a flaw in its cloud remote management service on November 20, 2026. This GL.iNet cloud zero-day let an unauthorized party “access and install malicious software on some GL.iNet routers and KVM devices.” The company has blocked the attack path and is shipping fixed firmware on November 22.
TL;DR
Exploitation in the wild is confirmed by GL.iNet itself. Blocking the cloud flaw stops new infections but does not clean devices that were already hit. Owners should check for the infection indicator and install the security firmware.
Why It Matters
Malware Stays After the Fix
The GL.iNet security notice is clear on this point. Its fixes “do not remove malware from devices that were already infected.” So patching alone is not enough for affected owners.
KVMs Reach Other Computers
GL.iNet KVM devices control the computers plugged into them. For that reason, GL.iNet is still “determining the scope of the incident, including whether computers connected to affected KVM devices were impacted.” It advises owners of infected KVMs to scan those computers too.
How the Attack Works
GL.iNet has not published technical details of the GL.iNet cloud zero-day. It says only that the flaw sat in its cloud remote management services, known as GoodCloud.
Meanwhile, the community has started its own analysis. A RemoteToHome incident page reports that the GoodCloud client on some routers passes an unchecked value from a cloud message to the shell. However, it has not tied that finding directly to the malware GL.iNet describes. The malware’s behavior and the number of infected devices remain unknown.
Affected Devices
- Some GL.iNet routers that use the cloud service
- GL.iNet KVM models, including RM1, RM1V2, RM1PE, RM4PE, RM10, RM10RC and RMQ1
GL.iNet will email customers it identifies as affected, using their cloud account address.
Patch and Mitigation
Check First
GL.iNet’s indicator is a running process containing crond -i /tmp/.log. Routers can be checked in LuCI’s process list, and KVMs through their web terminal. Community researchers suggest checking before rebooting, since some traces vanish on restart.
If You Find the Indicator
- Install the KVM security beta: 1.10.2 or later, or 1.8.6 for RMQ1.
- Alternatively, reset the device to factory settings.
- Change passwords, VPN keys and other secrets stored on the device.
For Everyone Else
Install the stable security firmware for your model once it is available. In addition, consider turning off GoodCloud if you do not need remote management. Finally, watch GL.iNet’s notice for updates on this GL.iNet cloud zero-day.
Support Our Threat Intelligence
Find our vulnerability reports and weekly recaps helpful? Support our work today and unlock a 100% ad-free reading experience!