CVE-2026-26791: 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, 14:05 UTC
- EPSS
- 2.5% chance of exploitation in 30 days – higher than 85% 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
To mitigate CVE-2026-26791, organizations should immediately restrict external network access to GL-iNet GL-AR300M16 devices by implementing firewall rules that limit management interfaces to trusted IP addresses only. Disable the echo server feature if it is not required, as this reduces the attack surface. Monitor network traffic and device logs for unusual commands or connections that could indicate exploitation attempts. Employ network segmentation to isolate vulnerable devices from critical infrastructure. Regularly check for firmware updates from GL-iNet and apply patches as soon as they become available. If a patch is not yet released, consider temporary device replacement or using alternative hardware. Additionally, implement intrusion detection/prevention systems (IDS/IPS) tuned to detect command injection patterns targeting this vulnerability. Educate network administrators about the risk and signs of compromise related to this vulnerability to ensure rapid incident response.
Description
GL-iNet GL-AR300M16 v4.3.11 was discovered to contain a command injection vulnerability via the string port parameter in the enable_echo_server function. This vulnerability allows attackers to execute arbitrary commands via a crafted input.