Skip to content
TrustList
Security advisories

GL.iNet says a cloud management flaw was used to plant malware on some routers and KVMs

Editorial

By TrustList Editorial

GL.iNet found on 20 November 2026 that an attacker used a flaw in its cloud remote management service to install malware on some routers and KVM devices; KVM beta fixes are out and stable firmware was scheduled for 22 November.

About GL.iNet says a cloud management flaw was used to plant malware on some routers and KVMs

GL.iNet says a cloud management flaw was used to plant malware on some routers and KVMs

20 November 2026: GL.iNet, which makes travel and small-office routers and remote KVM devices, says an attacker used a flaw in its cloud remote management service to install malicious software on some of its routers and KVMs. The company says it found the problem that day, closed the hole and blocked the access used, so devices can no longer be newly infected that way. Its notice is clear that this does not remove malware from devices that were already infected.

Not yet independently verified. All facts come from GL.iNet's own security notice, issued 20 November 2026 and last updated 21 November 2026, read on 22 November 2026. GL.iNet has not said how many devices or which router models were infected, and has not named the attacker. The notice gave 22 November as the date for stable firmware; we had not seen those builds when we read it. We will update this when it can be confirmed, and remove this note.

What GL.iNet has said

The notice was issued on 20 November and last updated on 21 November. It says:

  • the vulnerability was in GL.iNet's cloud remote management services, not in a single router model;
  • only some devices were infected, and the company has not said how many or which router models;
  • KVM firmware with security fixes is available now through the beta channel: 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;
  • stable firmware with security fixes for both routers and KVMs was scheduled for 22 November 2026;
  • customers it identifies as affected will be emailed at the address on their GL.iNet cloud account, with guidance for their device;
  • it is still working out the scope, including whether computers connected to affected KVMs were reached.

How to check a device

GL.iNet gives one sign of infection for both routers and KVMs: a running process showing crond -i /tmp/.log. On a router, open the admin panel, go to System, Advanced Settings, sign in to LuCI and look under Status, Processes, or run ps | grep tmp over SSH. On a KVM, open Toolbox, Terminal, Access and run the process list command the notice gives for your model, on the KVM itself and not on the connected computer.

If the sign is found, GL.iNet says to treat the device as infected: install the KVM beta now, or reset the device to factory settings, then install the stable security firmware once it is out. A reset cannot be reinfected through the fixed cloud flaw. If the check finds nothing and there is no other reason for concern, no reset is needed, but the update is still advised.

Steps for IT teams

  • List every GL.iNet router and KVM in use, including travel routers carried by staff, and check each one for the process above.
  • Install the stable security firmware as soon as it appears for each model.
  • For any infected KVM, check the computer attached to it for unfamiliar programs, browser extensions, user accounts, startup items and scheduled tasks, run a full scan, and change passwords used on it.
  • Consider turning off cloud remote management where it is not needed, and review whether out-of-band KVMs should be reachable from a vendor cloud at all.
  • Questions go to support@gl-inet.com; security reports to security@gl-inet.com.

Sources

Categories & features

TrustList Weekly

The week in software and IT, in one email

The news that matters to buyers, new rankings and our own research. Every Thursday, free, and easy to leave.

We will email you to confirm. Unsubscribe with one click in any issue. Privacy policy

You may be interested in