What is CVE-2016-6277?

CVE-2016-6277 is NETGEAR Multiple Routers Remote Code Execution Vulnerability. The supplied enrichment data classifies it as CSRF mapped to CWE-352 Cross-Site Request Forgery.

Which versions are affected?

Affected product and version evidence is listed in the product table above. Current public advisories should be checked for exact version scope before patch targeting is finalized.

Is there active exploitation?

Yes: CISA KEV signal present. If exploitation is not confirmed from current sources, teams should document that status and continue monitoring KEV, vendor, and telemetry updates.

Yes. The supplied enrichment data lists CVE-2016-6277 in CISA KEV with required action: Apply updates per vendor instructions.. KEV status should be monitored because it can change after initial disclosure or after exploitation becomes publicly confirmed.

Is there a public exploit?

26 public PoC repositories reported; 1 marked weaponized in current dataset. Public exploit or PoC availability should raise triage priority, especially for exposed or business-critical systems.

How can defenders detect it?

Start with web/proxy/WAF logs, application logs, network IDS/IPS where available. Look for vulnerability-class behavior, product errors, suspicious authentication events, exploit probes, and abnormal process activity based only on evidence that applies to the affected product.

How should teams prioritize it?

Prioritize CVE-2016-6277 using CVSS 8.8, EPSS 100%, KEV status, public PoC status, and asset exposure. Internet-facing, privileged, or business-critical deployments should be handled first.

Are workarounds available?

The supplied mitigation guidance says to apply vendor patches and restrict external exposure until fixed. Fixed-version evidence is listed in the mitigation section above.

Which threat actors are linked publicly?

Publicly linked actor or ransomware signals in the supplied enrichment data: TeamTNT (), Kinsing (). Do not attribute exploitation to a threat actor unless the source evidence explicitly supports that linkage.

What should be done in the next 24 hours?

Identify exposed assets running affected vendor/product/version combinations. Treat as emergency remediation because CISA KEV status is present. Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class. Open remediation tickets with affected assets, owners, evidence status, and detection coverage so decisions are traceable.

CISA KEVhighCSRFpublic exploit

CVE-2016-6277

CVE-2016-6277 — NETGEAR Multiple Routers Remote Code Execution Vulnerability

NETGEAR R6250 before 1.0.4.6.Beta, R6400 before 1.0.1.18.Beta, R6700 before 1.0.1.14.Beta, R6900, R7000 before 1.0.7.6.Beta, R7100LG before 1.0.0.28.Beta, R7300DST before 1.0.0.46.Beta, R7900 before 1.0.1.8.Beta, R8000 before 1.0.3.26.Beta, D6220, D6400, D7000, and possibly other routers allow remote attackers to execute arbitrary commands via shell metacharacters in the path info to cgi-bin/.

Published Dec 14, 2016Updated Jun 17, 2026Sources: NVD, NETGEAR (CNA), CISA, FIRST EPSS, Exploit-DB, SOCRadar CTI

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed Mar 7, 2022

EPSS

100%

top of FIRST's scoreset

Affects

NETGEAR

Multiple Routers

CVSS base

8.8

high · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade Multiple Routers to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA required action

Apply updates per vendor instructions.

Federal deadline Sep 7, 2022 — passed 1,467 days ago

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.
Treat as emergency remediation because CISA KEV status is present.
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
NETGEAR	Multiple Routers	—	Vulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

High

Confidentiality

High

Integrity

High

Scope

Unchanged

Attack Complexity

Low

Attack Vector

Network

Privileges Req

None

User Interaction

Required

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
8.8	CVSS 3.1	high	2.8	5.9	NVD, CNA
9.3	CVSS 2.0	high	8.6	10	NVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

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.

MITRE

CWE-352 · Cross-Site Request Forgery (CSRF)

Gain Privileges or Assume Identity
Bypass Protection Mechanism
Read Application Data
Modify Application Data

Mitigation: Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, use anti-CSRF packages such as the OWASP CSRFGuard. [REF-330] Another example is the ESAPI Session Management control, which includes a component for CSRF. [REF-45]

Weakness & attack patterns

CWE-352Cross-Site Request Forgery

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

CAPEC-462 · Cross-Domain Search TimingCAPEC-467 · Cross Site IdentificationCAPEC-62 · Cross Site Request ForgeryCAPEC-111 · JSON Hijacking (aka JavaScript Hijacking)

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

CISAThat month →

Listed

Mar 7, 2022

Federal deadline

Sep 7, 2022

passed 1,467 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

1 of the 5 sampled are weaponized

Exploit entries

Exploit-DB and CTI exploit indexes

Social mentions

Posts naming this CVE. Attention, not evidence of exploitation — it spikes on disclosure and decays whether or not anything is exploited.

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 /.
Prioritize edge telemetry for network-reachable Multiple Routers.
Monitor for scanner or exploit-pattern traffic after 26 public PoC repositories were reported.

web/proxy/WAF logsapplication logsnetwork IDS/IPS

Groups associated with this CVE

Groups reported in connection with this vulnerability. A reported association, not a confirmed observation of that group using it — and not scoped to any sector or campaign.

TeamTNTKinsing

ip91.92.40.11898
DShield-Firehol · Jun 14, 2026
ip83.150.218.9339
Collective Intelligence Network Security-Firehol · May 24, 2025
ip83.252.42.11259
Abuse.ch-Urlhaus-C&Cs · Jul 30, 2025
hash641292761cbff314e8214771cc645e97fb06b487
SOCRadar Threat Exchange Services · Jul 10, 2026
hash393216:5ldzraqgbkxmx6yqz2aidmefrnkeef7caumqjchzdfwkyxzro3zxdv4cgdc7fdoi:dikgiehogkg0z6defq+
SOCRadar Threat Exchange Services · Jul 10, 2026

2 more indicators on this CVEShowing 5 of 7 · Hashes, addresses and domains from a live threat exchangeUnlock free

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 8.8 (AV:N)
Jun 17, 2026 · NVD
2025
Bulletin released on Mitre.
Jul 28, 2025 · SOCRadar CTI
Bulletin released on NIST.
Jan 23, 2025 · SOCRadar CTI
2024
Bulletin released on NIST.
Jul 16, 2024 · SOCRadar CTI
2023
CVE is exploited. "Ostorlab/KEV"
Dec 26, 2023 · SOCRadar CTI
CVE is exploited. "ARPSyndicate/cvemon"
Dec 15, 2023 · SOCRadar CTI
CVE is exploited. "HimmelAward/Goby_POC"
Dec 15, 2023 · SOCRadar CTI
CVE is exploited. "Ostorlab/known_exploited_vulnerbilities_detectors"
Dec 15, 2023 · SOCRadar CTI
CVE is exploited. "philipcv/netgear-r7000_command_injection_exploit"
Dec 15, 2023 · SOCRadar CTI
CVE is exploited. "qazbnm456/awesome-cve-poc"
Dec 15, 2023 · SOCRadar CTI
CVE is exploited. "xbl3/awesome-cve-poc_qazbnm456"
Dec 15, 2023 · SOCRadar CTI
2022
Added to CISA KEV catalog
Mar 7, 2022 · CISA
CVE is exploited. "NETGEAR Multiple Routers Remote Code Execution Vulnerability"
Mar 7, 2022 · SOCRadar CTI
2020
Bulletin released on MITRE_REFERENCES.
Sep 16, 2020 · SOCRadar CTI
2017
Added · Verified remote entry: Netgear R7000 / R6400 - 'cgi-bin' Command Injection (Metasploit)
Mar 13, 2017 · Exploit-DB
Added · Verified remote entry: Netgear R7000 / R6400 - 'cgi-bin' Command Injection (Metasploit)
Mar 13, 2017 · Exploit-DB
2016
Initial · CVE published
Dec 14, 2016 · NVD
Added · Verified webapps entry: Netgear R7000 - Command Injection
Dec 7, 2016 · Exploit-DB

Source activity

Readings a source repeats on a schedule, counted rather than listed.

9×Github ReposMay 25, 2020 – Jul 28, 2023 · SOCRadar CTI
4×ModifiedJul 16, 2024 – Mar 14, 2025 · SOCRadar CTI
3×Tweets · 2 times tweeted.Feb 18, 2026 – Feb 19, 2026 · SOCRadar CTI
1×SVRS is calculatedFeb 22, 2026 · SOCRadar CTI

References

10 on the record

kb.netgear.com/000036386/CVE-2016-582384
Patch, Vendor Advisory, NIST, MITRE_REFERENCES
packetstormsecurity.com/files/155712/Netgear-R6400-Remote-Code-Execution.html
Exploit, Third Party Advisory, VDB Entry, NIST, MITRE_REFERENCES, GITHUB
www.securityfocus.com/bid/94819
Broken Link, Third Party Advisory, VDB Entry, NIST, Mitre
www.sj-vs.net/a-temporary-fix-for-cert-vu582384-cwe-77-on-netgear-r7000-and-r6400-routers/
Broken Link, Mitigation, Third Party Advisory, MITRE_REFERENCES, NIST
kalypto.org/research/netgear-vulnerability-expanded/
Broken Link, Exploit, Third Party Advisory, MITRE_REFERENCES, NIST
www.exploit-db.com/exploits/40889/
Third Party Advisory, VDB Entry, Vendor Advisory, Mitre, NIST, GITHUB
www.exploit-db.com/exploits/41598/
Exploit, Third Party Advisory, VDB Entry, Vendor Advisory, Mitre, NIST, GITHUB
www.kb.cert.org/vuls/id/582384
Third Party Advisory, US Government Resource, Mitre, NIST

Coverage

7 stories from the feeds we poll

2 more reports on this CVEShowing 5 of 7 · Vendor research and security press coverageUnlock free

Elsewhere on this site

NETGEARevery CVE for this vendor
March 2022what else CISA listed
CSRFsame class
CWE-352other 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.

Only the 5 indicator(s) reported for this CVE are available; no packet-level or host-forensic 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-2016-6277 is NETGEAR Multiple Routers Remote Code Execution Vulnerability, a high vulnerability affecting Multiple Routers from NETGEAR. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 26 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 8.8 describes technical severity, while EPSS 100% 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.