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

Back
New CVE Detected

CVE-2026-18614 – Unauthenticated Remote Code Execution – GL.iNet GL-MT3000 (Beryl AX) firmware 4.4.0

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-18614 is an unauthenticated command injection vulnerability in the GL.iNet GL-MT3000 (Beryl AX) router. A flaw in the s2s.so native plugin allows a remote, unauthenticated attacker to inject operating-system commands through the router’s web management interface, resulting in code execution as root. The issue is rated Critical.

Technical details

  • Root cause: The s2s.enable_echo_server method validates the port argument only by passing it through atoi() for a numeric range check (1–65534). atoi() stops parsing at the first non-digit character, so the original unsanitized string is retained and then passed into snprintf() and system(), allowing shell metacharacters to survive validation.
  • Trigger conditions: An attacker sends a POST request to /cgi-bin/glc invoking the s2s object’s enable_echo_server method with a crafted port argument (e.g. a value combining a valid leading number with appended shell metacharacters). No authentication is required.
  • Attack vector: Network — the vulnerable endpoint is reachable over the device’s HTTP management interface.
  • Impact: Full unauthenticated remote command execution with root privileges, leading to complete compromise of the device.

Affected software

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

Severity

  • 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
  • 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

Mitigation and recommended actions

  • Immediate: Upgrade GL-MT3000 firmware to a fixed release beyond 4.4.5 once published by the vendor; consult GL.iNet security updates for the corresponding patched version.
  • If no patch is available: Do not expose the router’s web management interface to the internet. Restrict access to the management interface (including /cgi-bin/glc) to trusted local networks via firewall rules, and disable remote 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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge