Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-18616 – Unauthenticated Command Injection (RCE) – GL.iNet GL-MT3000 firmware 4.4.0 through

Be the first to know when new zero-days emerge:

Summary

CVE-2026-18616 is an unauthenticated OS command injection vulnerability in the GL.iNet GL-MT3000 (Beryl AX) travel router. The flaw resides in the wg-server native plugin exposed through the /cgi-bin/glc interface and allows a remote, unauthenticated attacker to execute arbitrary commands as root. It is rated Critical (CVSS v4.0 9.3 / CVSS v3.1 9.8).

Technical details

  • Root cause: The wg-server.set_peer method (in /usr/lib/oui-httpd/rpc/wg-server.so) builds a shell command with sprintf() using the fixed template wg set wgserver peer %s allowed-ips %s persistent-keepalive 25 2>/dev/null. The attacker-supplied public_key value is inserted without shell metacharacter escaping or validation and the result is passed to system().
  • Trigger conditions: An HTTP POST request to /cgi-bin/glc invoking server.set_peer with a public_key value containing shell metacharacters (for example command substitution $(...)). The /cgi-bin/glc binary loads and invokes these plugin methods via dlopen()/dlsym() without any authentication check.
  • Attack vector: Network — no authentication and no user interaction required.
  • Impact: Arbitrary command execution with root privileges, leading to full compromise of the device (confidentiality, integrity, and availability).

Affected software

  • GL.iNet GL-MT3000 (Beryl AX) firmware versions 4.4.0 through 4.4.5.

Severity

  • CVSS v3.1 base score: 9.8 (Critical)CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
  • CVSS v4.0 base score: 9.3 (Critical) — CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade GL-MT3000 firmware beyond the affected 4.4.x branch to the latest release published on the GL.iNet security updates page.
  • If no patch can be applied immediately: Restrict access to the router’s administrative/HTTP interface so it is not reachable from the internet or untrusted networks (e.g., disable remote/WAN-side management and place the management interface behind a firewall or VPN), reducing exposure of the /cgi-bin/glc endpoint.

How IONIX identifies potentially affected assets

IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.

  • Page title: GL.iNet, GL-MT3000, Beryl AX, GL.iNet Admin Panel

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge