CVE-2020-26902
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 command injection by an unauthenticated attacker. 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 · high confidenceCommand injection vulnerability in NETGEAR Orbi mesh WiFi systems (RBK752, RBR750, RBS750, RBK852, RBR850, RBS850) allows unauthenticated remote attackers to execute arbitrary shell commands on affected devices due to insufficient input validation in the firmware before version 3.2.15.25.
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
- 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 exact Orbi model numberCheck the device label on the physical device or log into the web admin interface (usually at 192.168.1.1) and look for the model number displayed in the top-right or under Administration > Firmware UpdateAffected if The model is one of RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850. Other models are not affected by this CVE.
-
Check the current firmware versionIn the web admin interface, go to Administration > Firmware Update or look for the version number displayed in the admin dashboard. Alternatively, use the NETGEAR Orbi app and check the device information section.Affected if The firmware version is displayed. Note this version for comparison against the vulnerable range.
-
Compare installed version to the vulnerable rangeCompare the firmware version you found against the affected versions: < 3.2.15.25 for all listed models (RBK752, RBR750, RBS750, RBK852, RBR850, RBS850).Affected if The firmware version is lower than 3.2.15.25. For example, 3.2.14.10 would be vulnerable, while 3.2.15.25 or 3.2.16.0 would not be.
-
Check if the web management interface is network-accessibleAttempt to access the Orbi admin interface from an external network (outside your local LAN) or check router/firewall rules to see if ports 80/443 (HTTP/HTTPS) to the Orbi device are forwarded or exposed to the internet.Affected if The web admin interface is accessible from the internet (WAN). Even with vulnerable firmware, the CVE requires network access to the management interface to be exploitable.
You are affected if your Orbi device is one of the six listed models AND runs firmware version lower than 3.2.15.25 AND has its management interface network-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
Update affected NETGEAR Orbi devices to firmware version 3.2.15.25 or later. If immediate patching is not possible, restrict external network access to management interfaces.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26902 — 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-26902 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