If you use a GL.iNet router (popular small travel and VPN routers) or a GL.iNet Comet KVM (a small box that lets you control a computer remotely), check it this weekend. On November 20, 2026, GL.iNet said an unauthorized party exploited a vulnerability in its cloud remote management service to access some of its routers and KVM devices and install malicious software on them.
What Happened
- The attack: GL.iNet says the attacker used a flaw in its cloud remote management service, not a flaw you can fix by changing your Wi-Fi password, to install malware on "some" GL.iNet routers and KVM devices.
- What GL.iNet has done: it says it fixed the cloud vulnerability and blocked the access used in the incident, so devices can no longer be newly infected through this attack path. It also says this does not remove malware from devices that were already infected.
- What is not known yet: as of November 21, 2026, GL.iNet has not said how many devices were hit or which router models. It says it is still investigating, including whether computers connected to affected KVMs were impacted (GL.iNet; PrivacyAffairs).
- Emails: GL.iNet says it will email customers it identifies as affected, at the address on their GL.iNet cloud account. You don't need to wait for an email to check your device.
Why the KVMs Matter Most
A KVM-over-IP device sits between you and a computer and lets someone see that computer's screen and use its keyboard and mouse from anywhere. If the KVM is controlled by an attacker, the computer connected to it is at risk too. That is why GL.iNet also tells KVM owners to check the connected computer.
How to Check a GL.iNet Router
GL.iNet says to look for a running process that contains the exact text crond -i /tmp/.log.
- In the router's Admin Panel, go to System > Advanced Settings and sign in to LuCI.
- In LuCI, open Status > Processes.
- Press Ctrl+F (Command+F on a Mac), search for
tmp/.log, and see whether a process showscrond -i /tmp/.log.
If you use SSH, sign in to the router and run ps | grep tmp. A line that shows only the grep command itself is not a match.
How to Check a GL.iNet KVM
- In the KVM web interface, go to Toolbox > Terminal > Access. Run the command in the KVM's terminal, not on the connected computer.
- On the Comet Q (RMQ1), run
ps -a | grep tmp. On all other KVM models, runps -aux | grep tmp. - Look for
crond -i /tmp/.login the output.
What to Do Based on the Result
- You found the indicator: treat the device as infected. For a KVM, GL.iNet says you can install the security beta firmware now or factory reset the device. A factory reset erases your settings, so you'll need to set it up again. GL.iNet says a reset device can't be reinfected through the fixed cloud flaw.
- The check found nothing: if you have no other reason to suspect infection, GL.iNet says no reset or cleanup is needed. Still install the stable security update when it is released.
- You're not sure: GL.iNet asks you to contact support@gl-inet.com.
Firmware Fixes
- KVM beta firmware with security fixes is available now: version 1.10.2 beta or later for the RM10, RM10RC, RM1, RM1V2, RM1PE and RM4PE, and 1.8.6 beta or later for the RMQ1 (Comet Q).
- Stable firmware with security fixes for both routers and KVMs is scheduled for November 22, 2026, according to GL.iNet. It recommends installing it as soon as it is available, even if your check found nothing.
- PrivacyAffairs reports that the KVM beta won't be offered automatically unless you joined the beta program; you download it from GL.iNet's firmware download center and use Local Upgrade.
If Your KVM Was Infected: Check the Connected Computer
GL.iNet recommends checking the computer plugged into the KVM for:
- Unfamiliar programs, browser extensions or user accounts
- Unexpected startup items or scheduled tasks
- Unusual settings changes or network activity
Run a full scan with up-to-date security software.
MediaVision Analysis
Cloud remote management is convenient: you can reach your router or a computer from anywhere. But this incident shows the risk. When the vendor's cloud is breached, every device linked to it can be reached. If you don't actually use remote cloud access, consider turning it off or unbinding the device from the cloud account, and keep remote access behind a VPN you control. GL.iNet's notice changed several times in its first day, so check it again before you act.
How MediaVision Can Help
MediaVision helps homes and businesses in Anaheim and Orange County secure routers, remote-access tools and the computers behind them. We can:
- Check your router or KVM for the infection indicator and update the firmware
- Factory reset and set up your device again safely
- Scan and clean the computer connected to an affected KVM
- Set up secure remote access with a VPN
- Give you a clear, honest quote before any work starts
MediaVision Computer Repair
800 S Brookhurst St, Suite 1B3, Anaheim, CA 92804
Phone: (714) 888-5959
Book Now
Frequently Asked Questions
I have a GL.iNet router but never used its cloud service. Am I affected?
GL.iNet says the attack came through its cloud remote management service, but it has not published which devices or models were hit. The check takes a minute, so it's worth running, and the stable security firmware is recommended for everyone.
Can my device get infected again?
GL.iNet says it fixed the cloud vulnerability and that devices can no longer be newly infected through this attack path.
Do I have to factory reset?
According to GL.iNet's latest notice, only if you find the infection indicator (or install the KVM security beta instead). If the check finds nothing, install the stable update when it's released.
Is my computer at risk?
If it is connected to an infected KVM, check it as described above. GL.iNet is still investigating the impact on connected computers.