How severe is CVE-2017-6884?

CVE-2017-6884 has a CVSS score of 8.8/10, rated HIGH. Immediate patching is strongly recommended.

Which products are affected by CVE-2017-6884?

Affected package information for CVE-2017-6884 is not yet fully mapped. Check the official advisory links for details.

How do I patch CVE-2017-6884?

No patch has shipped for CVE-2017-6884 yet — track the zyxel emg2926 firmware advisory for a fixed release and apply the workarounds below in the meantime.

How do I detect CVE-2017-6884 across my infrastructure?

Inventory every zyxel emg2926 firmware deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.

How do I mitigate CVE-2017-6884 if there is no patch (or I can't update yet)?

Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.

How does O3 Security protect against CVE-2017-6884?

O3 detects and blocks CVE-2017-6884 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Is CVE-2017-6884 actively exploited in the wild?

Yes. There are 6 known exploit references for CVE-2017-6884, including 1 documented proof-of-concept exploit on Exploit-DB and 5 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2017-6884?

CVE-2017-6884 has an EPSS (Exploit Prediction Scoring System) score of 37.6%, placing it in the 98th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

Is CVE-2017-6884 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2017-6884 (Zyxel EMG2926 Routers Command Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2023-09-18. CISA required all US federal civilian agencies to remediate this vulnerability by 2023-10-09. The required action was: Apply mitigations per vendor instructions or discontinue use of the product if mitigations are unavailable. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2017-6884?

CVE-2017-6884 is classified as OS Command Injection (CWE-78). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2017-6884?

CVE-2017-6884 affects zyxel emg2926 firmware (1 version, e.g. v1.00\(aaqt.4\)b8). Check the affected-products list on this page against your deployed version to confirm exposure.

When was CVE-2017-6884 published, and has it been updated?

CVE-2017-6884 was published on April 6, 2017 and was last updated on June 17, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2023-09-18 — agencies required to remediate by 2023-10-09 · Ransomware

CVE-2017-6884

HIGH

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…

Published

Apr 6, 2017

Updated

Jun 17, 2026

Affected

0 pkgs

Patched

None yet

Exploits

6 known

EPSS Exploitation Probability

via FIRST.org ↗

37.6%probability of exploitation in next 30 days

Moderate Risk98th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

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.

Affected Products

1 product · 1 configurations

emg2926 firmwarezyxel

1 version

v1.00\(aaqt.4\)b8

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-41782webappshardware

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

by trevor Hough · Apr 2, 2017

Exploit-DB Source

Detection & mitigation playbook

Vendor / appliance

Detect
Inventory every zyxel emg2926 firmware deployment and check each version against the affected-products list above. Because the exploit targets the running system rather than your application code, also watch for remote code execution at the network and runtime layer — O3 flags the exploit behaviour from runtime telemetry and egress traffic even before a vulnerable build is confirmed.
Remediation status
No patch has shipped for CVE-2017-6884 yet — track the zyxel emg2926 firmware advisory for a fixed release and apply the workarounds below in the meantime.
Mitigate without a patch
Cut exposure now: restrict the management/admin interface to trusted networks, segment the device, and apply the vendor's recommended configuration mitigations and any WAF/IPS signature. O3's runtime protection blocks the exploit chain at execution, holding the line on unpatched or end-of-life systems until you can patch.
How O3 protects you
O3 detects and blocks CVE-2017-6884 exploitation at runtime: eBPF exploit-chain detection, plus L7 egress monitoring that catches the post-exploitation callback and severs the attacker's outbound channel.

Tailored to CVE-2017-6884. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Runtime Protection

Is CVE-2017-6884 being exploited in your environment?

O3's eBPF runtime sensors and L7 egress monitoring detect and block the CVE-2017-6884 exploit chain at execution — protecting unpatched and end-of-life systems until the vendor patch is applied.

Protect my workloads How runtime protection works

CVE-2017-6884

EPSS Exploitation Probability

Description

Affected Products

Detection & mitigation playbook

Detect

Remediation status

Mitigate without a patch

How O3 protects you

Frequently Asked Questions

Is CVE-2017-6884 being exploited in your environment?