CVE-2020-26908
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 authentication bypass. This affects D6200 before 1.1.00.36, D7000 before 1.0.1.74, PR2000 before 1.0.0.30, R6020 before 1.0.0.42, R6050 before 1.0.1.22, JR6150 before 1.0.1.22, R6080 before 1.0.0.42, R6120 before 1.0.0.66, R6220 before 1.1.0.100, R6230 before 1.1.0.100, R6260 before 1.1.0.64, R6700v2 before 1.2.0.62, R6800 before 1.2.0.62, R69002 before 1.2.0.62, 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 confidenceAuthentication bypass vulnerability in multiple NETGEAR router models (D6200, D7000, PR2000, R6020, R6050, JR6150, R6080, R6120, R6220, R6230, R6260, R6700v2, R6800, R6900v2, WNR2020) allows unauthenticated attackers to gain administrative access to the router firmware. The specific bypass mechanism is not detailed, but the critical CVSS score indicates remote, straightforward exploitation enabling full device compromise.
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.36< 1.0.1.74< 1.0.0.30< 1.0.0.42< 1.0.1.22< 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 modelLocate the model number on the device label or log into the router admin interface and check the status or administration page for the exact model designation (e.g., D6200, R6700v2, R6800)Affected if The model matches one of the following: D6200, D7000, PR2000, R6020, R6050, JR6150, R6080, R6120, R6220, R6230, R6260, R6700v2, R6800, R6900v2, WNR2020
-
Check installed firmware versionLog into the router web interface and navigate to Administration > Firmware Update or Router Status page to view the current firmware version; alternatively, check the version displayed on the main status dashboardAffected if Firmware version is below the threshold for your specific model (D6200: <1.1.00.36, D7000: <1.0.1.74, PR2000: <1.0.0.30, R6020: <1.0.0.42, R6050: <1.0.1.22, R6080: <1.0.0.42, R6120: <1.0.0.66, R6220: <1.1.0.100)
-
Verify remote administration is enabledIn the router admin interface, go to Advanced > Administration > Remote Management or Remote Access settings and check if Enable Remote Management is turned onAffected if Remote management is enabled and the admin interface is accessible from the WAN/internet side
Your router is affected if it is one of the listed models, runs firmware below the specified version threshold, and has remote administration enabled or exposed to an untrusted network
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.
dbcve · scoped1.0.0.301.0.0.421.0.0.66
Update router firmware to the specified minimum versions (e.g., D6200 to 1.1.00.36, R6700v2 to 1.2.0.62). If updates are unavailable, restrict administrative interface access to trusted networks only via firewall rules or VPN.
Model-specific: D6200 -> 1.1.00.36 | D7000 -> 1.0.1.74 | PR2000 -> 1.0.0.30 | R6020 -> 1.0.0.42 | R6050 -> 1.0.1.22 | R6080 -> 1.0.0.42 | R6120 -> 1.0.0.66 | R6220 -> 1.1.0.100
- 1. Identify the exact NETGEAR router model from the affected list (D6200, D7000, PR2000, R6020, R6050, R6080, R6120, R6220)
- 2. Check the current firmware version by logging into the router web interface or checking the device label
- 3. Download the appropriate fixed firmware version from the official NETGEAR support website (kb.netgear.com) for your specific model
- 4. Access the router administration panel and navigate to the Firmware Update or Administration section
- 5. Upload and install the new firmware file
- 6. After the router restarts, verify the firmware version has been updated to the fixed release
- 7. Consider resetting the admin password as a precautionary measure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26908 — 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-26908 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