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

Back
New CVE Detected

CVE-2026-18615 – 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-18615 is an unauthenticated OS command injection vulnerability in the GL.iNet GL-MT3000 (Beryl AX) router firmware. The flaw resides in the wg-server.generate_publickey method exposed through the /cgi-bin/glc RPC endpoint and allows a remote attacker to execute arbitrary commands as root. It is rated Critical.

Technical details

  • Root cause: The generate_publickey function in the wg-server.so native plugin (/usr/lib/oui-httpd/rpc/wg-server.so) interpolates the attacker-supplied private_key value directly into a shell command of the form echo %s | wg pubkey without sanitization.
  • Trigger conditions: A private_key value containing shell metacharacters (for example $(...) command substitution) is expanded by the shell before the wg pubkey pipe executes, yielding blind command execution.
  • Attack vector: Network-based via the unauthenticated /cgi-bin/glc RPC endpoint; no authentication or user interaction is required. Injection is delivered through the private_key field in the JSON args object of a wg-server.generate_publickey request.
  • Impact: Arbitrary command execution as root, leading to full remote code execution and complete compromise of 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)
  • 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: Monitor GL.iNet for a firmware release addressing this issue and upgrade GL-MT3000 devices as soon as a fixed version is published. At the time of writing, no fixed firmware version is confirmed in the CVE record.
  • If no patch: Do not expose the router’s administrative/RPC interface (/cgi-bin/glc) to the internet. Restrict management access to trusted networks or VPN, place the device behind a firewall, and monitor for anomalous requests to the wg-server.generate_publickey method.

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