CVE-2020-26901
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 sensitive information. This affects RBK752 before 3.2.15.25, RBR750 before 3.2.15.25, RBS750 before 3.2.15.25, RBK852 before 3.2.15.25, RBR850 before 3.2.15.25, and RBS850 before 3.2.15.25.
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 confidenceCertain NETGEAR Orbi mesh router systems (models RBK752, RBR750, RBS750, RBK852, RBR850, RBS850) contain a vulnerability in versions prior to 3.2.15.25 that allows an attacker to potentially obtain sensitive information. The specific attack vector, authentication requirements, and nature of the exposed data are not detailed in the available advisory.
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< 3.2.15.25< 3.2.15.25< 3.2.15.25< 3.2.15.25< 3.2.15.25< 3.2.15.25CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 Orbi model numberLocate the model number on the device label or access the router admin web interface (usually at 192.168.1.1 or orbilogin.com) and check the status or system info pageAffected if The model is one of RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850
-
Check the installed firmware versionIn the router admin interface, navigate to Administration > Firmware Update or Advanced > Administration > Firmware version. Alternatively, check the status page for the current firmware versionAffected if The firmware version displayed is earlier than 3.2.15.25 (for example, 3.2.14.10 or any version below 3.2.15.25)
-
Verify remote management settingsIn the admin interface, go to Advanced > Remote Management or Administration > Router Update and check if remote management access is enabled. Test accessing the router login page from an external network (outside your local LAN)Affected if Remote management or external admin access is enabled and the device is reachable from the internet
-
Check for unauthorized configuration changesReview the router configuration for unexpected port forwards, VPN configurations, or admin accounts that were not created by you. Compare current settings against a known-good backup if availableAffected if Unexpected configuration entries exist, particularly those that expose admin interfaces or create unauthorized access pathways
The device is affected if it is one of the listed Orbi models (RBK752, RBR750, RBS750, RBK852, RBR850, RBS850) running firmware version 3.2.15.25 or lower, especially if remote management is enabled or the device is internet-accessible.
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 data3.2.15.25
Apply NETGEAR firmware version 3.2.15.25 or later to affected devices. If immediate patching is not possible, restrict network access to trusted users and monitor for unauthorized access attempts.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26901 — 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-26901 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