CVE-2021-29076
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 RBK852 before 3.2.17.12, RBK853 before 3.2.17.12, RBK854 before 3.2.17.12, RBR850 before 3.2.17.12, and RBS850 before 3.2.17.12.
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 confidenceUnauthenticated command injection vulnerability in NETGEAR Orbi mesh WiFi systems (RBK852, RBK853, RBK854, RBR850, RBS850) allows remote attackers to execute arbitrary operating system commands on the affected devices via specially crafted requests, likely through insufficient input validation in the device's web management interface.
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.17.12< 3.2.17.12< 3.2.17.12< 3.2.17.12< 3.2.17.12CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:C/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 NETGEAR Orbi device modelLocate the model number on the device label or access the web management interface and check the device info page. Affected models are RBK852, RBK853, RBK854, RBR850, or RBS850.Affected if The device model is one of RBK852, RBK853, RBK854, RBR850, or RBS850.
-
Check the installed firmware versionLog into the web management interface (typically at 192.168.1.1 or orbilogin.com) and navigate to Administration > Firmware Update or similar. Record the current firmware version displayed.Affected if The firmware version is lower than 3.2.17.12.
-
Verify web management interface accessibilityAttempt to access the device's web management interface from your browser. Confirm whether the login page loads and is reachable.Affected if The web management interface is exposed and reachable on the network.
-
Review device for unexpected configuration changesCheck the web management interface for any unauthorized changes to settings, new port forwarding rules, or unknown connected devices.Affected if Unexpected changes are present that were not made by the administrator.
Your environment is affected if you own an RBK852, RBK853, RBK854, RBR850, or RBS850 device running firmware version 3.2.17.12 or lower, and the web management interface is 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.
dbcve · scoped3.2.17.12
Update NETGEAR Orbi firmware to version 3.2.17.12 or later. If immediate patching is not feasible, restrict external network access to the device management interfaces and monitor for indicators of compromise.
Firmware version 3.2.17.12 or later for Rbk852, Rbk853, Rbk854, Rbr850, Rbs850
- Access the NETGEAR Orbi web management interface by entering the router's IP address in a web browser
- Log in to the router administration panel with administrator credentials
- Navigate to the Administration or Settings section
- Look for a Firmware Update or Router Update option
- Check the current firmware version under the Router Status or About section
- If the current firmware version is below 3.2.17.12, download the latest firmware from the official NETGEAR support site (kb.netgear.com) for your specific model
- In the firmware update section, select the downloaded firmware file (.bin or .img file)
- Initiate the firmware upgrade and wait for the process to complete - do not power off the device during this process
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29076 — 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-29076 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