CVE-2020-26905
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 disclosure of administrative credentials. This affects CBR40 before 2.5.0.10, RBK752 before 3.2.15.25, RBR750 before 3.2.15.25, RBS750 before 3.2.15.25, RBK852 before 3.2.10.11, RBR850 before 3.2.10.11, and RBS850 before 3.2.10.11.
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 confidenceNETGEAR Orbi and Nighthawk mesh router devices contain a vulnerability allowing disclosure of administrative credentials. The flaw affects multiple device models in the CBR40, RBK752, RBR750, RBS750, RBK852, RBR850, and RBS850 product lines, enabling attackers to potentially obtain admin-level access.
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< 2.5.0.10< 3.2.15.25< 3.2.15.25< 3.2.15.25< 3.2.10.11< 3.2.10.11< 3.2.10.11CVSS 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 the device modelLocate the model number on the device label or access the router admin interface and check the status or system information page for the exact model designation (CBR40, RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850)Affected if The device model is any of the following: CBR40, RBK752, RBR750, RBS750, RBK852, RBR850, or S850
-
Locate the firmware versionAccess the router admin interface (typically at 192.168.1.1 or orbilogin.com), navigate to the Firmware Update or Administration section, and record the currently installed firmware version numberAffected if A firmware version is displayed that can be compared against the known vulnerable versions
-
Compare CBR40 firmware versionIf the device is a CBR40, check if the installed firmware version is lower than 2.5.0.10 by comparing the version numbers numerically or checking the exact version string in the admin interfaceAffected if The device is a CBR40 and the firmware version is earlier than 2.5.0.10
-
Compare RBK752/RBR750/RBS750 firmware versionIf the device is an RBK752, RBR750, or RBS750, verify whether the installed firmware version is earlier than 3.2.15.25 by checking the firmware version displayed in the admin interfaceAffected if The device is an RBK752, RBR750, or RBS750 and the firmware version is earlier than 3.2.15.25
-
Compare RBK852/RBR850/RBS850 firmware versionIf the device is an RBK852, RBR850, or RBS850, determine if the installed firmware version is lower than 3.2.10.11 by reviewing the version information in the router status or firmware sectionAffected if The device is an RBK852, RBR850, or RBS850 and the firmware version is earlier than 3.2.10.11
The device is affected if it is any of the listed models (CBR40, RBK752, RBR750, RBS750, RBK852, RBR850, RBS850) and its current firmware version falls below the corresponding threshold (2.5.0.10 for CBR40, 3.2.15.25 for RBK752/RBR750/RBS750, or 3.2.10.11 for RBK852/RBR850/RBS850).
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 data2.5.0.103.2.10.113.2.15.25
Update firmware to the patched versions: CBR40 to 2.5.0.10, RBK752/RBR750/RBS750 to 3.2.15.25, and RBK852/RBR850/RBS850 to 3.2.10.11. Restrict administrative interface access to trusted networks.
- Consultation1.0 h
- Implementation2.0 h
- Testing1.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 $1,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26905 — 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-26905 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