CVE-2020-26897
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 · high confidenceNETGEAR Orbi and CBR devices contain a vulnerability that allows unauthenticated attackers to obtain administrative credentials, likely through a backdoor, insecure storage, or an information disclosure flaw. This enables full administrative access to the affected devices.
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 your device modelLog into the router web interface (typically at 192.168.1.1 or 10.0.0.1) and navigate to Administration > Router/Device Information or check the product label on the physical device. Confirm the model is one of: CBR40, RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850.Affected if Device model matches any of the affected models listed above
-
Check installed firmware versionIn the router web interface, go to Administration > Firmware Update or Router/Device Information section. Record the current firmware version displayed.Affected if Firmware version is below 2.5.0.10 for CBR40, below 3.2.15.25 for RBK752/RBR750/RBS750, or below 3.2.10.11 for RBK852/RBR850/RBS850
-
Verify remote administration exposureIn the router web interface, check Settings > Advanced > Remote Management or similar. Determine if Remote Management is enabled and accessible from the internet.Affected if Remote Management is enabled and the device is internet-facing, increasing exposure to unauthenticated attackers
The device is affected if it is a CBR40, RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850 model running firmware versions below the respective thresholds (2.5.0.10, 3.2.15.25, or 3.2.10.11), as these versions contain the credential disclosure vulnerability.
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
Apply the vendor-supplied firmware updates: CBR40 to 2.5.0.10, RBK752/RBR750/RBS750 to 3.2.15.25, and RBK852/RBR850/RBS850 to 3.2.10.11 or later.
- 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-26897 — 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-26897 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