CVE-2026-9213
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 · uneditedA vulnerability in the affected NETGEAR gaming routers allows attackers with the ability to intercept and tamper with traffic between the router and the Internet, to execute code on the device.
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 confidenceThis vulnerability in NETGEAR gaming routers allows a man-in-the-middle attacker between the router and the Internet to inject malicious code and achieve remote code execution on the device. The vulnerability likely stems from a lack of proper integrity verification or encryption of communications between the router and external endpoints.
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.0.4.48< 1.0.4.48< 1.2.14.114< 1.0.2.86CVSS 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
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/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 router modelLog into the router web interface or check the device label to confirm the exact model number (Mr70, Ms70, Raxe500, or Xr1000)Affected if Router model is one of the four affected models listed in the CVE
-
Check installed firmware versionAccess the router web interface, navigate to Administration or Firmware Update section, and note the current firmware version; or use the command 'grep version /tmp/etc/passwd' or check the firmware file name if upgrades were performed manuallyAffected if Firmware version is below 1.0.4.48 for Mr70/Ms70, below 1.2.14.114 for Raxe500, or below 1.0.2.86 for Xr1000
-
Verify remote management statusIn the router web interface, check Settings > Remote Management or Administration > Remote Management to see if remote access from the internet is enabledAffected if Remote management is enabled and the router is directly exposed to the internet
-
Assess network exposureCheck if the router WAN interface has a public IP address and whether port forwarding or UPnP is configured to allow external traffic to reach internal servicesAffected if Router has direct WAN exposure with public IP and has port forwarding or UPnP enabled, increasing the attack surface for network-based exploitation
The environment is affected if the router is a Mr70, Ms70, Raxe500, or Xr1000 model running firmware below the specified version thresholds and the router is accessible from the internet.
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 · scoped1.0.2.861.0.4.481.2.14.114
Apply available firmware updates from NETGEAR for affected router models. Until patches are available, avoid operating the router on untrusted networks where an attacker could intercept and modify traffic.
Mr70: 1.0.4.48 | Ms70: 1.0.4.48 | Raxe500: 1.2.14.114 | Xr1000: 1.0.2.86
- 1. Identify your NETGEAR router model (Mr70, Ms70, Raxe500, or Xr1000)
- 2. Navigate to the official NETGEAR support website (support.netgear.com)
- 3. Enter your router model number in the search or product lookup
- 4. Locate the firmware download section for your specific model
- 5. Download the firmware version 1.0.4.48 for Mr70/Ms70, version 1.2.14.114 for Raxe500, or version 1.0.2.86 for Xr1000
- 6. Access your router's web management interface by entering the router's IP address in a web browser
- 7. Log in with your administrator credentials
- 8. Navigate to the Advanced tab and select Administration or Firmware Update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9213 — 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-2026-9213 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