CVE-2026-26793: GL-iNet GL-AR300M16 · Command Injection
Source CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 2.3% chance of exploitation in 30 days – higher than 83% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
- Monitor GL-iNet’s official channels for firmware updates addressing CVE-2026-26793 and apply patches promptly once available.
- Until patches are released, restrict remote access to the router’s management interface by limiting access to trusted IP addresses and disabling remote administration features.
- Implement network segmentation to isolate GL-iNet routers from critical infrastructure and sensitive data environments, reducing lateral movement risk.
- Employ intrusion detection/prevention systems (IDS/IPS) to monitor for suspicious command injection attempts targeting the set_config function or unusual device behavior.
- Regularly audit router configurations and logs for signs of compromise or unauthorized changes.
- Educate users and administrators about the risks of exposing device management interfaces to the internet and encourage strong password policies.
- Consider replacing affected devices with models that have a stronger security track record if immediate patching is not feasible.
Description
GL-iNet GL-AR300M16 v4.3.11 was discovered to contain a command injection vulnerability via the set_config function. This vulnerability allows attackers to execute arbitrary commands via a crafted input.