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

New CVE Detected

CVE-2026-18685 – Unauthenticated Command Injection (RCE) – GL.iNet GL-MT3000 (Beryl AX) firmware 4.4

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

Summary

CVE-2026-18685 is an unauthenticated command injection vulnerability in GL.iNet GL-MT3000 (Beryl AX) routers. The flaw resides in the set_upgrade function exported by the modem.so library and reachable through the /cgi-bin/glc endpoint, allowing a remote attacker to execute arbitrary commands as root without credentials. It is rated Critical.

Technical details

  • Root cause: The set_upgrade handler in modem.so embeds the attacker-controlled firmware_upload parameter directly into a shell command via sprintf() without quoting or sanitization, and executes it through /bin/sh -c. The existence check performed before this validates the modem_url value but not firmware_upload.
  • Trigger conditions: An attacker sends a crafted JSON request to /cgi-bin/glc invoking object=modem, method=set_upgrade, with shell metacharacters (for example &(command);#) placed in the firmware_upload field.
  • Attack vector: Network — reachable remotely over HTTP against the device’s web interface, requiring no authentication and no user interaction (CWE-77 / CWE-74 command injection).
  • 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 through 4.4.5.

Severity

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

Mitigation and recommended actions

  • Immediate: Update GL-MT3000 devices to the latest firmware available from GL.iNet’s official firmware and security-updates channels, and verify the running version is no longer within the 4.4.0–4.4.5 range.
  • If no patch can be applied yet: Do not expose the router’s web/administration interface (/cgi-bin/glc) to the internet. Restrict management access to trusted LAN clients or a VPN, and place the device behind a firewall that blocks inbound access to the HTTP interface from untrusted networks.

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