# CVE-2026-18598: GL.iNet GL-MT3000 Logread Lua RPC plugin logread logread.get_system_log command injection

> Remote attackers can execute arbitrary commands on GL.iNet GL-MT3000 routers via the logread Lua RPC plugin.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 3 Aug 2026
- **Updated:** 3 Aug 2026
- **Also known as:** GHSA-35v2-77rf-53pc

## What is CVE-2026-18598?

CVE-2026-18598 is a high-severity command injection vulnerability in GL.iNet GL-MT3000, published on 3 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was detected in GL.iNet GL-MT3000 up to 4.4.5. The affected element is the function logread.get_system_log of the file /usr/lib/oui-httpd/rpc/logread of the component Logread Lua RPC plugin. The manipulation of the argument module results in command injection. The attack can be launched remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure and confirmed the existence of the vulnerability.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

## Which versions are affected by CVE-2026-18598?


## How do I fix CVE-2026-18598?

No fix has been published for CVE-2026-18598 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-18598 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-18598 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-18598 and fix it if it is affected.

What it is: CVE-2026-18598 is a high-severity command injection vulnerability in GL.iNet GL-MT3000, published on 3 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-18598 exists.

Affected product: GL.iNet GL-MT3000. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-18598/ (Markdown: https://insights.sbomify.com/CVE-2026-18598/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-18598
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-18598
- OSV: https://osv.dev/vulnerability/CVE-2026-18598

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-18598/
Summaries are generated and may contain mistakes; the official description above is the record.