CVE-2021-45558
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 authenticated user. This affects RBK752 before 3.2.16.6, RBR750 before 3.2.16.6, RBS750 before 3.2.16.6, RBK852 before 3.2.16.6, RBR850 before 3.2.16.6, and RBS850 before 3.2.16.6.
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 is an authenticated command injection vulnerability in NETGEAR Orbi mesh WiFi systems (RBK752, RBR750, RBS750, RBK852, RBR850, RBS850). An authenticated attacker can inject and execute arbitrary operating system commands through improper input sanitization in the device's web interface or API, potentially compromising the entire mesh 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.16.6< 3.2.16.6< 3.2.16.6< 3.2.16.6< 3.2.16.6< 3.2.16.6CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:H/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 Orbi device modelLocate the model number on the device label or access the router web interface and check the hardware version or product name. Confirm it matches one of: RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850.Affected if The device model is one of the listed affected models.
-
Check installed firmware versionLog into the Orbi web interface (typically at 192.168.1.1 or orbilogin.com). Navigate to Administration > Firmware Update or Settings > Router/Orbi Settings to view the current firmware version number.Affected if The firmware version is lower than 3.2.16.6 (for example, 3.2.14.5 or any version < 3.2.16.6).
-
Confirm web management interface is enabledAttempt to access the device web interface from the network. Check if HTTP/HTTPS ports 80 or 443 are listening on the router's LAN IP address.Affected if The web management interface is accessible and responds to requests.
-
Verify authentication statusDetermine if the administrative interface is protected by credentials. Check if default credentials are in use or if any user account has administrative access.Affected if Administrative access is available with valid credentials or default credentials are unchanged.
If the device is an affected Orbi model (RBK752, RBR750, RBS750, RBK852, RBR850, or RBS850) running firmware version lower than 3.2.16.6, and its web interface with administrative authentication is accessible, the environment is vulnerable to CVE-2021-45558.
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.
dbcve · scoped3.2.16.6
Update the firmware on all affected Orbi devices to version 3.2.16.6 or later. Restrict administrative access to trusted users only and avoid exposing the device management interface to untrusted networks.
Firmware version 3.2.16.6 or later for Rbk752, Rbr750, Rbs750, Rbk852, Rbr850, and Rbs850
- Identify the exact NETGEAR Orbi model (Rbk752, Rbr750, Rbs750, Rbk852, Rbr850, or Rbs850)
- Access the router's web administration interface by navigating to routerlogin.net or the device's IP address
- Navigate to the Administration or Settings section to check the current firmware version
- Download firmware version 3.2.16.6 or later from the official NETGEAR support website (kb.netgear.com) for your specific model
- In the router admin interface, locate the firmware update section and upload the downloaded firmware file
- Wait for the firmware upload and installation to complete - do not power off the device during this process
- After reboot, verify the firmware has been updated by checking the version in the admin interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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-2021-45558 — 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-2021-45558 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