CVE-2020-26916
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedCertain NETGEAR devices are affected by incorrect configuration of security settings. This affects D6200 before 1.1.00.38, D7000 before 1.0.1.78, JR6150 before 1.0.1.24, R6020 before 1.0.0.42, R6050 before 1.0.1.24, R6080 before 1.0.0.42, R6120 before 1.0.0.66, R6220 before 1.1.0.100, R6260 before 1.1.0.64, R6700v2 before 1.2.0.62, R6800 before 1.2.0.62, R6900v2 before 1.2.0.62, R7450 before 1.2.0.50, and WNR2020 before 1.1.0.62.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceMultiple NETGEAR router models (D6200, D7000, JR6150, R6020-R6950v2 series, R7450, WNR2020) contain incorrect security settings in their default configuration. The specific nature of the misconfiguration is not detailed in the available description, but it allows an attacker to potentially exploit the security settings.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.1.00.38< 1.0.1.78< 1.0.1.24< 1.0.0.42< 1.0.1.24< 1.0.0.42< 1.0.0.66< 1.1.0.100CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Adjacent
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify router modelLog into the router web interface (typically at 192.168.1.1) and check the device status page, or look at the device label on the router itself. Common model numbers include D6200, D7000, JR6150, R6020, R6050, R6080, R6120, R6220, R7450, WNR2020, or R6700v2/R6850/R6950v2 series.Affected if The router model is one of the affected models listed in the CVE (D6200, D7000, JR6150, R6020-R6950v2 series, R7450, WNR2020)
-
Determine firmware versionIn the router web interface, navigate to Administration > Router Update or Advanced > Administration > Firmware Update to view the current firmware version. Alternatively, check the status or settings page for the firmware version string.Affected if Firmware version cannot be determined or is not visible in the interface
-
Compare version against affected thresholdsMatch your router model and firmware version to the following thresholds: D6200 < 1.1.00.38, D7000 < 1.0.1.78, JR6150 < 1.0.1.24, R6020 < 1.0.0.42, R6050 < 1.0.1.24, R6080 < 1.0.0.42, R6120 < 1.0.0.66, R6220 < 1.1.0.100. For R6700v2/R6850/R6950v2/R7450/WNR2020, compare to the R6020-R6950v2 series range.Affected if Your installed firmware version is lower than the version threshold for your specific model
-
Verify default configuration exposureSince the CVE describes incorrect security settings in the default configuration, attempt to access router services from an untrusted network position. Check if default services (such as remote management, UPnP, or admin interfaces) are exposed on WAN interfaces when they should not be.Affected if Router services or admin interfaces are accessible from WAN when not intentionally enabled by the user
A user is affected if they own one of the listed NETGEAR router models and their firmware version falls below the specified threshold for that model, indicating the default security misconfiguration is present.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor data1.0.0.421.0.0.661.0.1.24
Update affected NETGEAR devices to the specified minimum firmware versions (e.g., D6200 to 1.1.00.38, R6220 to 1.1.0.100, R6700v2 to 1.2.0.62) to remediate the security misconfiguration.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26916 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2020-26916 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data