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

Back
New CVE Detected

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

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-18612 is an unauthenticated OS command injection vulnerability (CWE-77) in the GL.iNet GL-MT3000 (Beryl AX) router. The flaw resides in the native plugins.so package-management component and allows a remote attacker to execute arbitrary commands as root. It is rated Critical.

Technical details

  • Root cause: the install_package and remove_package functions in the plugins.so native plugin (/usr/lib/oui-httpd/rpc/plugins.so) take the user-supplied package name and pass it into a shell command string built with sprintf and executed via system(), without sanitizing shell metacharacters.
  • Trigger conditions: an attacker sends a crafted request to the /cgi-bin/glc endpoint invoking plugins.install_package or plugins.remove_package with a name value containing shell metacharacters (for example a semicolon-delimited command). Input validation only blacklists a few private package name prefixes via strstr(), which does not block metacharacters.
  • Attack vector: network, unauthenticated, no user interaction required.
  • Impact: arbitrary command execution with root privileges, leading to 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)
  • Vector: 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 the latest version published by GL.iNet on its security updates portal. No fixed version is stated in the public CVE record; consult the vendor advisory to confirm the patched release before upgrading.
  • If no patch can be applied: do not expose the router’s web/management interface (/cgi-bin/glc) to untrusted or internet-facing networks. Restrict management access to trusted hosts via firewall rules or VLAN segmentation, and disable remote administration until patched.

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