CVE-2026-0411
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 · uneditedAn information disclosure vulnerability in the NETGEAR Orbi satellites (RBR/RBE/RBS Series) could allow a user connected to your network to gain administrator access to the Orbi router. The listed NETGEAR models are affected by this vulnerability. Orbi WiFi Systems without satellite devices are not impacted by this issue.
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 confidenceAn information disclosure vulnerability in NETGEAR Orbi satellite devices (RBR/RBE/RBS Series) allows a network-adjacent user to gain administrator access to the Orbi router. The vulnerability stems from improper protection of sensitive information that can be leveraged to escalate privileges. Systems without satellite devices are not affected.
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< 9.13.2.1< 4.4.2.2< 6.3.8.11< 4.4.2.2< 6.3.8.11CVSS 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.
-
Confirm Orbi satellite device presenceLog into the Orbi router web interface or mobile app and navigate to the Connected Devices or Satellite status section. Look for any satellite devices listed (RBR, RBE, or RBS series).Affected if No satellite devices are connected - the vulnerability only affects systems with satellite devices
-
Identify the exact satellite modelIn the router admin interface, locate the device information or firmware section for each connected satellite. Note the full model number (e.g., RBE970, RBR350, RBR760, RBS350, RBS760).Affected if The model is NOT one of: RBE970, RBR350, RBR760, RBS350, or RBS760 - these are the only affected models
-
Check router firmware versionIn the router admin interface, go to Settings > Administration > Firmware Update or similar. Record the current firmware version displayed.Affected if The firmware version is lower than the affected threshold: RBE970 < 9.13.2.1, RBR350/RBS350 < 4.4.2.2, RBR760/RBS760 < 6.3.8.11
-
Verify satellite firmware versionIn the router admin interface, check the firmware version listed for each connected satellite device.Affected if Any satellite device runs firmware below its respective threshold (same version thresholds as step 3)
-
Assess network accessibilityReview network configuration to determine if untrusted or unauthorized users could access the local network adjacent to the Orbi devices.Affected if The local network is accessible to untrusted users - the attacker requires network adjacency to exploit this vulnerability
The environment is affected if Orbi satellite devices (RBE970, RBR350, RBR760, RBS350, or RBS760) are connected and running firmware versions below the listed thresholds, and the network allows adjacent attackers.
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 · scoped4.4.2.26.3.8.119.13.2.1
Apply available NETGEAR firmware updates for affected Orbi satellite models when released. Until then, restrict network access to trusted users only and monitor for unauthorized administrative access attempts.
RBE970: 9.13.2.1+ | RBR350/RBS350: 4.4.2.2+ | RBR760/RBS760: 6.3.8.11+
- 1. Identify your specific Orbi model from the affected list (RBE970, RBR350, RBR760, RBS350, or RBS760)
- 2. Log in to the Orbi router web interface by entering the router's IP address in a web browser
- 3. Navigate to the Administration or Settings section and check the current firmware version under 'Router Info' or 'Firmware Update'
- 4. Visit the NETGEAR support website (support.netgear.com) and search for your specific model number
- 5. Download the latest firmware version for your model: RBE970 requires 9.13.2.1 or later; RBR350/RBS350 require 4.4.2.2 or later; RBR760/RBS760 require 6.3.8.11 or later
- 6. In the router web interface, go to the 'Firmware Update' or 'Advanced > Administration > Firmware Update' section
- 7. Click 'Browse' or 'Choose File' and select the downloaded firmware file
- 8. Click 'Upload' or 'Update' to begin the firmware installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0411 — 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-0411 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