Skip to content

CVE-2016-6277

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/.

CVSS
8.8Highscored by CISA
Exploited in the wild
Yes, in CISA KEV since 7 Mar 2022CISA deadline for US federal agencies: 7 Sept 2022public exploit code
EPSS
99.8%chance of exploitation in the next 30 daystop 0.1% of scored CVEsFIRST score of 11 Nov 2026
Fix
Patch availablesee the advisories in the references
Published
14 Dec 2016analysed here 12 Nov 2026

Do first. Apply updates per vendor instructions. (CISA's required action for this KEV entry)

Summary

Triage

Attack surface
Client-side
Exploitable
At runtime
Attack vector
network
Weakness
  • CWE-352 Cross-Site Request Forgery (CSRF)
Can a WAF block it?
Partly. See why

The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.

Affected products

Products named in our analysis

  • netgear:d6220_firmware
  • netgear:d6400_firmware
  • netgear:r6250_firmware
  • netgear:r6400_firmware
  • netgear:r6700_firmware
  • netgear:r6900_firmware
  • netgear:r7000_firmware
  • netgear:r7100lg_firmware
  • netgear:r7300dst_firmware
  • netgear:r7900_firmware
  • netgear:r8000_firmware

Fix and mitigation

WAF and other mitigations

Can a WAF block it? Partly. CSRF requests look like normal user actions. A WAF can enforce Origin and Referer checks, but the real fix is in the application.

Also consider: SameSite cookies · CSRF tokens

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

Remediation steps (AI-written)

Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.

Exploitation evidence

CISA KEV catalog
Listed since 7 Mar 2022.
CISA due date
7 Sept 2022, the remediation deadline for US federal agencies
CISA required action
Apply updates per vendor instructions.
Public exploit code
Yes: 3 on Exploit-DB · 1 Metasploit module · 1 Nuclei template
CISA SSVC
exploitation active, automatable no, technical impact totalAssessed by CISA 4 Feb 2025 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.

Exploit-DB

Metasploit

Nuclei

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

Timeline

  1. 7 Dec 2016First public exploit or proof of concept
  2. 14 Dec 2016Published8 days later
  3. 7 Mar 2022Added to CISA KEV (exploited in the wild)1,908 days (about 5 years) later
  4. 7 Sept 2022CISA remediation due date (US federal agencies)184 days (about 6 months) later
  5. 4 Feb 2025CISA SSVC assessment: exploitation active882 days (about 2 years) later
  6. 21 Oct 2025CVE record last updated259 days (about 9 months) later
  7. 12 Nov 2026Analysed by vulneraibility.com387 days (about 1 year) later

CVSS vector

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

MetricValueWhat it means
Attack vectorNetworkReachable over the internet or any routable network.
Attack complexityLowRepeatable attack, no special conditions.
Privileges requiredNoneThe attacker needs no prior access.
User interactionRequiredA victim must click, open or otherwise cooperate.
ScopeUnchangedImpact stays within the vulnerable component.
ConfidentialityHighTotal data disclosure possible.
IntegrityHighComplete modification possible.
AvailabilityHighFull outage possible.

Common questions

Is CVE-2016-6277 being exploited?

Yes. CVE-2016-6277 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2016-6277?

CVE-2016-6277 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2016-6277?

Yes. A fix has been recorded for CVE-2016-6277. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2016-6277 affect?

CVE-2016-6277 affects netgear:d6220_firmware, netgear:d6400_firmware, netgear:r6250_firmware, netgear:r6400_firmware, and 7 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

References

NVDCVE.orgCVE DetailsSource

9 references in the CVE record, grouped by the tags the record gives them.

Advisories (1)

Exploits (2)

Other links (6)

Where the data on this page comes from

Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.

Similar CVEs

Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.

© 2026 vulneraibility.com