CVE-2026-11450
Description
GL.iNet GL-MT3000 firmware 4.4.5 has a command injection vulnerability in the RPC handler, allowing remote code execution.
AI Insight
LLM-synthesized narrative grounded in this CVE's description and references.
GL.iNet GL-MT3000 firmware 4.4.5 has a command injection vulnerability in the RPC handler, allowing remote code execution.
Vulnerability
A command injection vulnerability exists in the glc CGI binary of GL.iNet GL-MT3000 devices running firmware version 4.4.5. The vulnerability resides in the path normalization handler, specifically within the dlopen function of the /usr/lib/oui-httpd/rpc/ library. By manipulating the dev_name argument passed to the eject_disk_do1 function, an attacker can achieve command injection [1].
Exploitation
An unauthenticated remote attacker can exploit this vulnerability by sending a specially crafted POST request to the /cgi-bin/glc endpoint. The request body should be in JSON format, specifying the nas-web object and the eject_disk_do1 method. The dev_name argument within the JSON payload must be carefully constructed to include padding and a shell command, such as /null$(cmd>/tmp/out), which bypasses initial validation and leads to command execution via /bin/sh -c [1].
Impact
Successful exploitation of this vulnerability allows an unauthenticated remote attacker to execute arbitrary commands on the affected GL.iNet GL-MT3000 device. This can lead to a full compromise of the device with the privileges of the running web server process [1].
Mitigation
GL.iNet has addressed this vulnerability in firmware version 4.7 and later by enabling method-level validation at the HTTP /rpc layer, removing nas-web.eject_disk from the allowed methods whitelist. Users are advised to upgrade to version 4.7 or a later version to mitigate this issue. The vendor confirmed that directly calling eject_disk through the default /rpc endpoint now returns Invalid params, preventing the exploit chain [1].
AI Insight generated on Jun 7, 2026. Synthesized from this CVE's description and the cited reference URLs; citations are validated against the source bundle.
Affected products
3Patches
0No patches discovered yet.
Vulnerability mechanics
No source-code context for this CVE — mechanics is only generated when we can read the actual fix diff. Without that, the four sections (root cause, attack vector, affected code, fix) would be speculation rather than analysis.
References
5News mentions
0No linked articles in our index yet.