CVE-2020-26929
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 R6220 before 1.1.0.100 and R6230 before 1.1.0.100.
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 confidenceAuthenticated command injection vulnerability in NETGEAR R6220 and R6230 routers allowing remote attackers to execute arbitrary system commands by injecting them into web interface parameters. The vulnerability exists in versions prior to 1.1.0.100.
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< 1.1.0.100< 1.1.0.100CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:A/AC:L/PR:L/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 router modelAccess the router's web management interface or check the device label to confirm the exact model number (R6220 or R6230).Affected if The device is a NETGEAR R6220 or R6230 router.
-
Check the installed firmware versionLog into the router web interface, navigate to the Administration or Advanced settings section, and locate the firmware version displayed. Alternatively, check the version information page. Compare this version to 1.1.0.100.Affected if The firmware version is below 1.1.0.100 (for example, 1.0.0.50 or similar).
-
Determine if the web management interface is accessible remotelyVerify whether the router's web interface is reachable from external networks. This can be done by checking router firewall settings, port forwarding rules, or by attempting to access the router's WAN IP from an untrusted network.Affected if The web management interface is accessible from untrusted networks or the WAN side.
-
Verify if remote management is enabledIn the router web interface, go to Advanced > Administration > Remote Management (or similar section) and check if remote management access is enabled.Affected if Remote management is enabled and allows access from non-local IP addresses.
-
Confirm authentication is required for the web interfaceVerify that the router's web interface requires login credentials. Attempt to access the interface without credentials or check the authentication settings.Affected if The web interface accepts authentication, which is required for exploiting this vulnerability.
A user is affected if they have a NETGEAR R6220 or R6230 router running firmware version below 1.1.0.100 with the web management interface accessible (especially remotely) and remote management enabled.
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 data1.1.0.100
Upgrade NETGEAR R6220 and R6230 firmware to version 1.1.0.100 or later. If immediate patching is not possible, limit access to the device management interface to trusted networks or IP addresses only.
- Consultation3.0 h
- Implementation2.0 h
- Testing4.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 $3,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-26929 — 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-26929 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