Skip to content
GL.iNet Security Notice 2026-11

GL.iNet Security Notice 2026-11

Gl-Inet • November 21, 2026

On November 20, 2026, GL.iNet identified a vulnerability in its cloud remote management services. An unauthorized party exploited the vulnerability to access and install malicious software on some GL.iNet routers and KVM devices.

The attack path has been blocked. We fixed the cloud vulnerability and blocked the access used in this incident. Devices can no longer be newly infected through this attack path. These measures do not remove malware from devices that were already infected.

Security firmware: Stable firmware with security fixes for both routers and KVM devices is scheduled for November 22, 2026 . We recommend installing the stable update for your model as soon as it becomes available, even if the check finds no signs of infection.

Follow the steps below to check your device. For both routers and KVM devices, look for the exact text crond -i /tmp/.log within the details of a running process. The process entry may contain other information.

If you find the indicator: Treat your device as infected. For a KVM, you can install the security beta for your model now using the links below. You can also restore your device to factory settings to address the infection. A factory reset erases your settings and requires you to set up the device again. The cloud vulnerability has been fixed, so a reset device cannot be reinfected through that vulnerability. Whether you install the beta or reset your device, we still recommend installing the latest stable security firmware for your model as soon as it is available.

If the check completes without finding the indicator: If you have no other reason to suspect infection, no factory reset or other cleanup is needed. The stable security update is still recommended.

If you cannot complete the check or are unsure the result: support@gl-inet.com for help.

How to check a GL.iNet router

Option 1: Use the web admin panel (LuCI)

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 macOS) and for tmp/.log . Check whether a matching process shows crond -i /tmp/.log .

Sign in to your router via SSH and run:

Look for crond -i /tmp/.log in the output. A line showing only the grep command is not a match.

How to check a GL.iNet KVM

In the KVM web interface, go to Toolbox → Terminal → Access . Run the command for your model in the KVM’s terminal, not on the connected computer.

All other KVM models:

Look for crond -i /tmp/.log in the output. A line showing only the grep command is not a match.

If your KVM is infected, also check the connected computer

As a precaution, check for unfamiliar programs, browser extensions or user accounts; unexpected startup items or scheduled tasks; and unusual settings changes or network activity. Run a full scan with up-to-date security software.

KVM security firmware downloads

KVM security fixes are already available through the beta channel for the models listed below. If your KVM shows signs of infection, you can install the beta update for your model now.

RM10 : 1.10.2 beta or later

RM10RC : 1.10.2 beta or later

RM1 : 1.10.2 beta or later

RM1V2 : 1.10.2 beta or later

RMQ1 : 1.8.6 beta or later

RM1PE : 1.10.2 beta or later

RM4PE : 1.10.2 beta or later

Firmware release, customer notifications, and investigation

Firmware release: KVM beta builds with security fixes are available now. Stable builds with security fixes for both routers and KVM devices are scheduled for November 22, 2026 .

Customer notifications: We will notify customers we identify as affected by email at the address associated with their GL.iNet cloud account. These emails will include device-specific guidance. You do not need to wait for an email to check your device or install the update.

Ongoing investigation: We are still determining the scope of the incident, including whether computers connected to affected KVM devices were impacted. We will update this notice as we confirm new information.

For questions, please support@gl-inet.com .

To report a security issue, security@gl-inet.com .

We apologize for the concern this may cause and are committed to keeping you informed.

GL.iNet Security Team

Founded in 2010, GL.iNet is a leading provider of innovative routers and networking solutions. From compact travel routers to cutting-edge remote KVMs, GL.iNet delivers award-winning networking technology designed for performance and security.

GL.iNet gives people and organizations the power to connect with confidence. By putting control in the hands of users, GL.iNet supports the productivity and collaboration that shape a Good Life.

The full story

This article is one source in a clustered incident — the cluster page carries the summary, timeline and every other outlet covering it.

GL.iNet cloud remote management flaw exploited to install malware on routers and KVMs On November 20, 2026, GL.iNet identified a vulnerability in its cloud remote management services that an unauthorized party exploited to access and install malicious software on some GL.iNet routers and KVM devices. GL.iNet states the attack path has been blocked and the cloud vulnerability fixed, so devices cannot be newly infected through it, but this does not remove malware from already-infected devices. GL.iNet's first notice says stable security firmware for routers and KVMs is scheduled for November 22, 2026, and recommends installing it even where no infection is found. Infection can be checked by looking for the exact text 'crond -i /tmp/.log' in running processes, via LuCI or SSH on routers and the KVM web terminal on KVMs. Where the indicator is found, the company says a factory reset clears the infection, or a security beta is available for KVMs now. For KVMs, GL.iNet advises checking connected computers for unfamiliar programs, extensions, accounts, startup items, and unusual network activity. A second GL.iNet notice on its forum describes the same incident in less detail, says a firmware update with additional protections is being prepared, and says affected customers will be notified by email. That notice also says the investigation into the full scope, including possible impact on computers connected to affected KVMs, is ongoing. No CVE identifier, exact number of affected devices, or threat actor attribution appears in the articles. 2 sources 57

Extracted Entities