CVE-2020-26911
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 lack of access control at the function level. 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.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 · high confidenceThis vulnerability is a broken access control at the function level in multiple NETGEAR router models. Affected devices allow unauthenticated or unauthorized users to access certain administrative functions due to missing authorization checks on specific API endpoints or operations. This could enable attackers to modify router settings, potentially leading to credential theft, network redirection, or 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.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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/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 your NETGEAR router modelLocate the model number on the device label or check the admin interface status pageAffected if The model is one of: D6200, D7000, Jr6150, R6020, R6050, R6080, R6120, or R6220
-
Determine the installed firmware versionLog into the router admin interface (typically at 192.168.1.1) and navigate to Administration > Firmware Update or Router Status to view the current firmware versionAffected if The firmware version is below the threshold for your model (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)
-
Check if remote management is enabledIn the router admin interface, go to Advanced > Remote Management and verify if the 'Enable Remote Management' checkbox is selectedAffected if Remote management is enabled and the router is accessible from the internet on WAN port 80/443
-
Test for unauthorized API endpoint accessFrom a non-authenticated browser or curl request, attempt to access common admin API paths such as /NCSAPI.xml or /board_data.cgi and observe if sensitive router configuration data is returned without loginAffected if Sensitive administrative data or configuration is returned without requiring authentication credentials
You are affected if your router model matches the listed products AND your firmware version is below the specified threshold, especially if remote management or the admin interface is exposed to untrusted networks.
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 the firmware on affected NETGEAR devices to the specified minimum versions (e.g., D6200 to 1.1.00.38, R6700v2 to 1.2.0.62). If immediate patching is not possible, restrict administrative access to trusted IPs only and disable remote management where not required.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26911 — 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-26911 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