CVE-2026-19982
CVE-2026-19982 — GL.iNet BE9300/MT6000 Firewall-management RPC os command injection
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."
Published Updated Sources: NVD, GL.iNet (CNA), GitHub, SOCRadar CTI
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Reported
not confirmed by CISA
EPSS
0%
ahead of 0% of scored CVEs
CVSS base
7.4
high · 6 sources
Remediation
The vendor's own words where we have them.
Upgrade BE9300 to a fixed release (4.9.0). Apply vendor patches per advisory and restrict external exposure of the affected component until patched.
First 24 hours
Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.
- Identify exposed assets running affected vendor/product/version combinations.
- Prioritize based on EPSS, PoC availability, and external exposure.
- Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.
Affected scope
Vendor, product and version as the advisories word them.
| Vendor | Product | Versions | Status |
|---|---|---|---|
| GL.iNet | BE9300 | 4.8.* | Vulnerable |
| GL.iNet | BE9300 | 4.9.0 | Patched |
| GL.iNet | MT6000 | 4.8.* | Vulnerable |
| GL.iNet | MT6000 | 4.9.0 | Patched |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Availability
Low
Confidentiality
Low
Integrity
Low
Scope
Changed
Attack Complexity
Low
Attack Vector
Network
Privileges Req
Low
User Interaction
None
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 7.4 | CVSS 3.1 | high | 3.1 | 3.7 | NVD |
| 6.5 | CVSS 2.0 | medium | 8 | 6.4 | vuldb.com (CNA) |
| 5.3 | CVSS 4.0 | medium | — | — | GL.iNet (CNA) |
| 7.4 | CVSS 3.1 | high | — | — | GL.iNet (CNA) |
| 7.4 | CVSS 3.0 | high | — | — | GL.iNet (CNA) |
| 6.5 | CVSS 2.0 | medium | — | — | GL.iNet (CNA) |
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:L
What this weakness leads to
MITRE's own consequences and mitigations for the weakness class — the authority's wording, not guidance derived from the CVSS vector.
CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')
- Execute Unauthorized Code or Commands
- DoS: Crash, Exit, or Restart
- Read Files or Directories
- Modify Files or Directories
Mitigation: If at all possible, use library calls rather than external processes to recreate the desired functionality.
CWE-77 · Improper Neutralization of Special Elements used in a Command ('Command Injection')
- Execute Unauthorized Code or Commands
Mitigation: If at all possible, use library calls rather than external processes to recreate the desired functionality.
Weakness & attack patterns
- CWE-78OS Command Injection
- CWE-77Command Injection
Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.
Public exploit
Capability, not use: code existing is a different claim from anyone running it.
Repositories
5
1 of the 5 sampled are weaponized
Detection
Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.
- Search application, proxy, and WAF logs for requests touching /dest_ip.
- Prioritize edge telemetry for network-reachable BE9300, MT6000.
- Monitor for scanner or exploit-pattern traffic after 5 public PoC repositories were reported.
Timeline
What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.
- 2026
Added · CVSS 3.1 7.4 (AV:N)
Aug 17, 2026 · NVD
Initial · CVE published
Aug 17, 2026 · NVD
CVE published by mitre
Aug 17, 2026 · SOCRadar CTI
Reported · Advisory disclosed
Aug 16, 2026 · GL.iNet
Reported · VulDB entry created
Aug 16, 2026 · GL.iNet
Reported · VulDB entry last update
Aug 16, 2026 · GL.iNet
Source activity
Readings a source repeats on a schedule, counted rather than listed.
- 1×CVE modified by NIST, Cweid, Modified, LinkAug 17, 2026 · SOCRadar CTI
References
5 on the record
- github.com/gl-inet/CVE-issues/blob/main/4.0.0/Firewall%20Cleanup%20RCE.md
Exploit, Third Party Advisory, NIST
- vuldb.com/cve/CVE-2026-19982
Vendor Advisory
- vuldb.com/submit/873918
Vendor Advisory
- vuldb.com/vuln/391164
Vendor Advisory
- vuldb.com/vuln/391164/cti
Vendor Advisory
Coverage
1 story from the feeds we poll
Elsewhere on this site
- GL.iNetevery CVE for this vendor
- Remote Code Execsame class
- CWE-78other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1
What should defenders know first?
CVE-2026-19982 is GL.iNet BE9300/MT6000 Firewall-management RPC os command injection, a high vulnerability affecting BE9300, MT6000 from GL.iNet. The current evidence does not list it in CISA KEV, and the exploit status is: Exploitation is reported, but no independent confirmation is available in the sources we have. Public exploit evidence is: 5 public PoC repositories reported; 1 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 7.4 describes technical severity, while EPSS 0% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.