Root command execution via unsanitized module parameter
Published Mar 12, 2026 · Updated Mar 12, 2026
Command injection in GL-iNet GL-AR300M16 firmware 4.3.11 allows remote authenticated users to execute arbitrary commands as root. M.get_system_log in logread.lua passes the module value into string.format and embeds the result in a shell command without sanitization or validation. A valid administrative session token is required by the published request, after which injected shell syntax runs with root privileges.
Summary
What happened
Command injection in GL-iNet GL-AR300M16 firmware 4.3.11 allows remote authenticated users to execute arbitrary commands as root. M.get_system_log in logread.lua passes the module value into string.format and embeds the result in a shell command without sanitization or validation. A valid administrative session token is required by the published request, after which injected shell syntax runs with root privileges.
The record
- CVE
- CVE-2026-26795
- Published
- Mar 12, 2026
- Updated
- Mar 12, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-77, T1059.004
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 12, 2026CVE publishedPublication date reported by the CVE source.
- Mar 12, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GL-AR300M16 get_system_log JSON-RPC proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo