PatchSiren cyber security CVE debrief
CVE-2026-18602 GL.iNet CVE debrief
A vulnerability was determined in GL.iNet GL-MT3000 up to 4.4.5. Affected is the function ovpn-client.get_recommend_config of the file /cgi-bin/glc of the component ovpn-client.so Native Plugin. Executing a manipulation of the argument Hostname can lead to command injection. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized. The vendor was contacted early about this disclosure and confirmed the existence of the vulnerability.
- Vendor
- GL.iNet
- Product
- GL-MT3000
- CVSS
- HIGH 8.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-08-03
- Original CVE updated
- 2026-10-23
- Advisory published
- 2026-08-03
- Advisory updated
- 2026-10-23
Who should care
Defenders responsible for GL.iNet GL-MT3000 devices, particularly those running firmware up to 4.4.5, should assess exposure and verify the effectiveness of current security controls.
Why it matters
Defenders should prioritize verifying exposure of GL.iNet GL-MT3000 devices running firmware up to 4.4.5 and assess the effectiveness of current security controls to prevent command injection attacks.
- Verify exposure of GL.iNet GL-MT3000 devices running firmware up to 4.4.5
- Assess the effectiveness of current security controls to prevent command injection attacks
- Implement compensating controls to prevent command injection attacks
Technical summary
The vulnerability is located in the ovpn-client.get_recommend_config function of the /cgi-bin/glc file in the ovpn-client.so Native Plugin. An attacker can execute a command injection attack by manipulating the Hostname argument. This affects GL.iNet GL-MT3000 devices running firmware up to 4.4.5. Defenders should prioritize verifying exposure and assessing the effectiveness of current security controls to prevent command injection attacks. The attack can be executed remotely and has been publicly disclosed. The vendor confirmed the existence of the vulnerability.
Defensive priority
Defenders should prioritize verifying exposure of GL.iNet GL-MT3000 devices running firmware up to 4.4.5 and assess the effectiveness of current security controls.
Recommended defensive actions
- Verify exposure of GL.iNet GL-MT3000 devices running firmware up to 4.4.5
- Assess the effectiveness of current security controls
- Implement compensating controls to prevent command injection attacks
- Review vendor patch guidance
- Conduct exposure review
- Implement monitoring
- Update asset inventory
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected product. Additional information is available from Vuldb. The vulnerability affects GL.iNet GL-MT3000 devices running firmware up to 4.4.5. Defenders should verify exposure and assess security controls. Evidence is limited, and further verification is required.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-18602 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-18602
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-18602 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-18602
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/StrTzz123/iot_vul/blob/main/GL-iNet/MT3000/4.4.5/ovpn_get_recommend_config_glc_rce/CVE.md
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/cve/CVE-2026-18602
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/submit/851542
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/385517
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/385517/cti
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.