basicsecurity.net
Proof, not just disclosure.
Threats / Zyxel / CVE-2017-6884
CVE-2017-6884 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Zyxel EMG2926 Routers vulnerability

Zyxel EMG2926 routers contain a command injection vulnerability in diagnostic tools that allows remote code execution through the nslookup function, enabling attackers to execute arbitrary commands on affected devices.

Verdict

Today item, not a backlog item.

This OS command injection vulnerability in widely deployed router firmware presents severe risk. Active exploitation in ransomware campaigns and high EPSS score indicate immediate threat. Affected organizations should prioritize patching or isolating vulnerable EMG2926 devices.

CISA KEV Yes · 2023-09-183Ransomware use Flagged3EPSS 0.37634 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
10 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2023-09-18), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.37634 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Zyxel, EMG2926 Routers. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-78 OS Command Injection — weakness family: Injection.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I identify the diagnostic nslookup endpoint and craft a malicious ping_ip parameter containing shell metacharacters to break out of the intended command context.
Business
Attackers gain unauthenticated remote code execution on network perimeter devices, establishing persistent access to internal infrastructure.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I execute system commands with router privileges to disable security controls, modify firewall rules, or establish reverse shells for command and control.
Business
Compromised routers become pivot points for lateral movement into corporate networks, bypassing external security controls.
3

Lateral reach — past segmentation narrative 3

Attacker
I deploy ransomware payloads or data exfiltration tools across the network using the router as a distribution vector.
Business
Ransomware campaigns encrypt critical business systems and threaten data breaches, resulting in operational shutdown and financial extortion.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • 10 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by mitre (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by mitreCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.