Threats / NETGEAR / CVE-2016-10174
CVE-2016-10174
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
NETGEAR WNR2000v5 Router vulnerability
NETGEAR WNR2000v5 routers are vulnerable to remote code execution via a buffer overflow, allowing unauthenticated attackers to gain complete control of affected devices.
Verdict
Today item — known-exploited.
A buffer overflow in the WNR2000v5 enables remote code execution without authentication. The high EPSS score and confirmed wild exploitation indicate active abuse. Organizations using this router model face immediate risk of compromise and should apply patches or replace the device.
CISA KEV Yes · 2022-03-254EPSS 0.8345 (verify live)5CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3Exploit Weaponized · public exploit · Metasploit module10
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
3 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 2022-03-25).
Probability (EPSS)
EPSS 0.8345 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: NETGEAR, WNR2000v5 Router. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-119 Memory Buffer Bounds Error — weakness family: Memory safety.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1880 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a functional/weaponized public exploit). Catalog entries: Metasploit module. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution 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 board1
Front door — unauthenticated access narrative 1
Attacker
I scan for exposed WNR2000v5 routers on the internet and identify vulnerable firmware versions.
Business
Attackers gain a foothold into the network perimeter, bypassing the organization's first line of defense.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I craft a malicious packet that triggers the buffer overflow and inject shellcode to execute arbitrary commands.
Business
The router is compromised with attacker code running at system privilege level.
3
Lateral reach — past segmentation narrative 3
Attacker
I establish persistent access, install backdoors, and pivot to internal network resources.
Business
The organization loses control of network infrastructure and faces data exfiltration, lateral movement, and potential ransomware deployment.
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