PatchSiren cyber security CVE debrief
CVE-2026-18616 GL-iNet CVE debrief
A vulnerability was identified in GL-iNet GL-MT3000 up to 4.4.5. The impacted element is the function server.set_peer of the file /cgi-bin/glc of the component wg-server.so Native Plugin. The manipulation of the argument public_key leads to command injection. Remote exploitation of the attack is possible. The exploit is publicly available and might be used.
- 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 in IoT or network security roles, should assess exposure and verify the effectiveness of current security controls.
Why it matters
The vulnerability allows for remote command injection, which could lead to unauthorized access and control of affected devices.
- Verify exposure of GL-iNet GL-MT3000 devices running firmware up to 4.4.5
- Assess the effectiveness of current security controls
- Monitor for potential exploitation attempts
Technical summary
The vulnerability is caused by a command injection issue in the server.set_peer function of the /cgi-bin/glc file in the wg-server.so Native Plugin of GL-iNet GL-MT3000 devices running firmware up to 4.4.5. This allows for remote exploitation, potentially leading to unauthorized access and control of affected devices. 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. The manipulation of the argument public_key leads to command injection.
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
- Monitor for potential exploitation attempts
- Review compensating controls for exposed systems while remediation is scheduled and verified
- Check relevant monitoring, detection, and logs for exposed assets that need extra review
- Track exceptions, retest remediated assets, and close the item only after evidence is documented
- Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
Evidence notes
The CVE record and NVD entry provide details on the vulnerability, but the actual impact and affected scope require verification from the supplied official sources. Defenders should verify the existence of GL-iNet GL-MT3000 devices running firmware up to 4.4.5 and assess the effectiveness of current security controls. The exploit is publicly available, and defenders should monitor for potential exploitation attempts.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-18616 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-18616
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-18616 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-18616
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/wg_set_peer_rce/CVE.md
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/cve/CVE-2026-18616
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/submit/851580
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/385536
-
Source reference
Unverified legacy reference
URL: https://vuldb.com/vuln/385536/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.