# CVE-2026-19982: GL.iNet BE9300/MT6000 Firewall-management RPC os command injection

> Remote attackers can execute arbitrary OS commands on GL.iNet BE9300 and MT6000 routers via the firewall-management RPC interface.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/E:X`)
- **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:** 17 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-3gr2-27fr-g5v9

## What is CVE-2026-19982?

CVE-2026-19982 is a medium-severity command injection vulnerability in GL.iNet BE9300, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in GL.iNet BE9300 and MT6000 4.8.x. This vulnerability affects unknown code of the component Firewall-management RPC. The manipulation of the argument dest_port/dest_ip leads to os command injection. The attack may be initiated remotely. Upgrading to version 4.9.0 is able to resolve this issue. The affected component should be upgraded. The vendor explains: "After our investigation, we have confirmed that the vulnerability described (...) does indeed exist."

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command), CWE-77 (Improper Neutralization of Special Elements used in a Command)

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


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

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

## Is CVE-2026-19982 being exploited?

There is no known exploitation of CVE-2026-19982 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-19982 is a medium-severity command injection vulnerability in GL.iNet BE9300, published on 17 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-19982 in the wild and no public exploit code.

Affected product: GL.iNet BE9300. 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-19982/ (Markdown: https://insights.sbomify.com/CVE-2026-19982/index.md)
```

## Sources

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

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