# CVE-2017-6884: Zyxel EMG2926 Routers Command Injection

> Attackers can execute arbitrary commands on Zyxel EMG2926 routers via the nslookup diagnostic tool, requiring immediate firmware updates.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 18 Sep 2023 (CISA KEV), used in ransomware
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Apr 2017
- **Updated:** 1 Oct 2026
- **Also known as:** GHSA-x6r5-p9fx-6346

## What is CVE-2017-6884?

CVE-2017-6884 is a high-severity command injection vulnerability in n/a, published on 6 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A command injection vulnerability was discovered on the Zyxel EMG2926 home router with firmware V1.00(AAQT.4)b8. The vulnerability is located in the diagnostic tools, specifically the nslookup function. A malicious user may exploit numerous vectors to execute arbitrary commands on the router, such as the ping_ip parameter to the expert/maintenance/diagnostic/nslookup URI.

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

## Which versions are affected by CVE-2017-6884?

It affects 1 product.


Products: Zyxel Emg2926 Firmware.

## How do I fix CVE-2017-6884?

No fix has been published for CVE-2017-6884 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 9 Oct 2023.

## Is CVE-2017-6884 being exploited?

Yes. Attackers have exploited CVE-2017-6884 in the wild since at least 18 Sep 2023, including in ransomware campaigns.

Public exploit code:

- Zyxel_ EMG2926 < V1.00(AAQT.4)b8 - OS Command Injection (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-6884 and fix it if it is affected.

What it is: CVE-2017-6884 is a high-severity command injection vulnerability in n/a, published on 6 Apr 2017. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2017-6884 in the wild since at least 18 Sep 2023, including in ransomware campaigns.

Affected product: n/a. 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-2017-6884/ (Markdown: https://insights.sbomify.com/CVE-2017-6884/index.md)
```

## Sources

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

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