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

New CVE Detected

CVE-2026-18686 – Pre-Authentication Command Injection (RCE) – GL.iNet GL-MT3000 firmware 4.4.0 throu

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

Summary

CVE-2026-18686 is a pre-authentication command injection vulnerability in the nas-web RPC wrapper of GL.iNet GL-MT3000 (Beryl AX) routers. An unauthenticated, network-based attacker can inject shell commands that execute as root, leading to remote code execution and full device compromise. The issue is rated critical (CVSS v4.0 9.3).

Technical details

  • Root cause: A two-stage (second-order) injection flaw in the nas-web RPC interface exposed at /cgi-bin/glc. The nas-web.add_user method writes the supplied password value into the nas_user table of /etc/config/gl_nas/file_share.db without sanitization or shell escaping.
  • Trigger conditions: A subsequent call to nas-web.add_share with proto=samba and the previously created user in the users[] array retrieves the stored password and passes it into a shell command (smbpasswd) via the backend service gl_nas_sys, executing it without escaping.
  • Attack vector: Network, unauthenticated — both nas-web.add_user and nas-web.add_share are reachable without credentials and require no user interaction.
  • Impact: Blind command execution with root privileges, enabling full compromise of confidentiality, integrity, and availability. Because the payload is stored, exploitation can be staged over time.

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 v4.0 base score: 9.3 (Critical) — Vector: 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) — 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 to a firmware release later than 4.4.5 once available from GL.iNet, and monitor the vendor’s security update channel for the fixed build.
  • If no patch: Do not expose the router’s web/administration and NAS interfaces to the internet. Restrict access to /cgi-bin/glc to trusted management networks, disable the Samba/NAS file-sharing feature if not required, and place the device behind a firewall that blocks inbound access to management and NAS ports.

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