CVE-2020-14426
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 RBK752 before 3.2.15.25, RBK753 before 3.2.15.25, RBK753S before 3.2.15.25, RBR750 before 3.2.15.25, RBS750 before 3.2.15.25, RBK852 before 3.2.10.11, RBK853 before 3.2.10.11, RBR850 before 3.2.10.11, RBS850 before 3.2.10.11, RBK842 before 3.2.10.11, RBR840 before 3.2.10.11, and RBS840 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 confidenceThis vulnerability allows disclosure of administrative credentials on affected NETGEAR Orbi mesh WiFi systems (RBK752, RBK753, RBK753S, RBR750, RBS750, RBK852, RBK853, RBR850, RBS850, RBK842, RBR840, RBS840). An unauthenticated or authenticated attacker could obtain administrative credentials, enabling full administrative access to the device and network.
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.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 Orbi model numberCheck the product label on the device bottom or access the web admin interface at orbilogin.com or 192.168.1.1 and look for the model name displayed on the dashboard or in the router settings.Affected if The model is one of: RBK752, RBK753, RBK753S, RBR750, RBS750, RBK852, RBK853, RBR850, RBS850, RBK842, RBR840, or RBS840.
-
Check the current firmware versionIn the Orbi web interface, navigate to Settings > Advanced > Router Update or look for a Firmware Version field on the main dashboard. Alternatively, open the NETGEAR Orbi app and select the router to view firmware information.Affected if A firmware version is displayed that can be compared to the affected ranges.
-
Compare version for RBK752/753/753S/RBR750/RBS750 modelsIf your model is RBK752, RBK753, RBK753S, RBR750, or RBS750, compare your installed firmware version number against 3.2.15.25.Affected if The installed version is lower than 3.2.15.25 (for example, 3.2.14.XX or earlier).
-
Compare version for RBK852/853/RBR850/RBS850 modelsIf your model is RBK852, RBK853, RBR850, or RBS850, compare your installed firmware version number against 3.2.10.11.Affected if The installed version is lower than 3.2.10.11 (for example, 3.2.9.XX or earlier).
-
Note RBK842/RBR840/RBS840 model statusThese models are listed as affected but specific version thresholds were not provided in the advisory. Treat any firmware version as potentially vulnerable unless NETGEAR has published a fixed version for these models.Affected if The device is an RBK842, RBR840, or RBS840 running any firmware version below what NETGEAR has released as a fix.
The environment is affected if the Orbi model matches the listed products and the installed firmware version falls below the threshold for its model family (3.2.15.25 for RBK752/753/753S/RBR750/RBS750, or 3.2.10.11 for RBK852/853/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 data3.2.10.113.2.15.25
Update firmware to version 3.2.15.25 or later for RBK752/753/753S/RBR750/RBS750 models, and version 3.2.10.11 or later for RBK852/853/RBR850/RBS850/RBK842/RBR840/RBS840 models.
- Consultation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-14426 — 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-14426 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