CVE-2026-26792: 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.8% chance of exploitation in 30 days – higher than 86% 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
Immediate mitigation involves isolating affected GL-iNet GL-AR300M16 devices from untrusted networks to prevent remote exploitation. Network administrators should implement strict firewall rules to restrict access to the router’s management interfaces, especially from external networks. Monitoring network traffic for unusual command execution patterns or unexpected firmware upgrade requests can help detect exploitation attempts. Since no official patches are available yet, consider deploying compensating controls such as network segmentation to limit the impact of a compromised device. Users should subscribe to GL-iNet security advisories for updates on patches and apply firmware updates promptly once released. Additionally, disabling remote management features and changing default credentials can reduce exposure. For critical environments, replacing vulnerable devices with models from vendors with timely security support is advisable until a fix is available.
Description
GL-iNet GL-AR300M16 v4.3.11 was discovered to contain multiple command injection vulnerabilities in the set_upgrade function via the modem_url, target_version, current_version, firmware_upload, hash_type, hash_value, and upgrade_type parameters. These vulnerabilities allow attackers to execute arbitrary commands via a crafted input.