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

New CVE Detected

CVE-2026-18601 – Unauthenticated Remote Code Execution (Command Injection) – GL.iNet GL-MT3000 firmw

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

Summary

CVE-2026-18601 is an unauthenticated command injection vulnerability in the GL.iNet GL-MT3000 (Beryl AX) router. The flaw resides in the ovpn-client.check_config function exposed through the /cgi-bin/glc RPC endpoint and allows a remote attacker to execute arbitrary commands as root. It is rated critical, and a public exploit is available.

Technical details

  • Root cause: The native plugin ovpn-client.so wraps a user-supplied filename in single quotes and passes it to a tar command executed via system(). A single-quote character in the filename closes the quoted context early, permitting shell command injection.
  • Trigger conditions: A single HTTP POST request to /cgi-bin/glc with a JSON body invoking the ovpn-client object’s check_config method, supplying a crafted filename argument (e.g. ';{command};#.tar.gz).
  • Attack vector: Network. The endpoint is reachable without authentication and requires no user interaction.
  • Impact: Arbitrary command execution as root, giving full compromise of confidentiality, integrity, and availability of the device.

Affected software

  • GL.iNet GL-MT3000 (Beryl AX) firmware versions 4.4.0, 4.4.1, 4.4.2, 4.4.3, 4.4.4, and 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)

Mitigation and recommended actions

  • Immediate: Upgrade to the latest firmware released by GL.iNet for the GL-MT3000. Monitor the GL.iNet Security Updates page for the fixed release, as no fixed version is confirmed in the primary sources reviewed.
  • If no patch is available: Do not expose the router’s web/management interface (/cgi-bin/glc) to the internet or untrusted networks. Restrict management access to trusted hosts via firewall rules or a VPN, and disable remote (WAN) administration.

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