dbcve.org
Rbe970 FirmwareOperating system · Netgear

CVE-2026-3088

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 7.2.7.15 / 9.10.1.4 or later.
See remediation →
70/100
Remediation priority · Elevated
No privileges Zero-click

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 · unedited
Unauthenticated users on the local network can cause the router to become unavailable by sending specially crafted requests.

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 confidence

This is a Denial of Service vulnerability in network router firmware that allows any unauthenticated user connected to the local network to render the router unavailable by sending specially crafted malicious requests. The attack requires only local network access and does not require authentication credentials.

MitigationApply available firmware updates from the router vendor; if no update exists, implement network segmentation or access control lists to restrict which local devices can communicate with the router's 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
Rbe970 FirmwareOperating system
Affected:< 9.10.1.4
Rbe971 FirmwareOperating system
Affected:< 9.10.1.4
Rbr860 FirmwareOperating system
Affected:< 7.2.7.15
Rbre950 FirmwareOperating system
Affected:< 7.2.7.15
Rbre960 FirmwareOperating system
Affected:< 7.2.7.15
Rbs860 FirmwareOperating system
Affected:< 7.2.7.15
Rbse950 FirmwareOperating system
Affected:< 7.2.7.15
Rbse960 FirmwareOperating system
Affected:< 7.2.7.15

CVSS 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
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Netgear router model
    Log into the router admin interface or check the device label to determine the exact model number (Rbe970, Rbe971, Rbr860, Rbre950, Rbre960, Rbs860, Rbse950, or Rbse960)
    Affected if The model is any of these eight affected models: Rbe970, Rbe971, Rbr860, Rbre950, Rbre960, Rbs860, Rbse950, or Rbse960
  2. Check the installed firmware version
    Access the router admin interface, typically at 192.168.1.1 or 192.168.1.254, and navigate to the Firmware Update or Administration section to view the current firmware version. Alternatively, check the Netgear Nighthawk or Orbi app if used for router management.
    Affected if For Rbe970 or Rbe971: firmware version is below 9.10.1.4. For Rbr860, Rbre950, Rbre960, Rbs860, Rbse950, or Rbse960: firmware version is below 7.2.7.15
  3. Verify network accessibility of the management interface
    Check if the router web interface (HTTP/HTTPS on ports 80/443) is accessible from network segments that contain untrusted devices. Use a scanner or attempt to access the router IP from a guest or IoT network segment.
    Affected if The router management interface is reachable from untrusted or guest network segments without network segmentation in place
  4. Confirm the router is still responsive
    Ping the router default gateway IP and attempt to access the admin login page via HTTP/HTTPS to verify the device is operational and not already crashed or hung due to exploitation.
    Affected if The router is unresponsive to ping or admin interface requests, indicating a potential denial of service condition

A user is affected if they own any of the eight listed Netgear models (Rbe970, Rbe971, Rbr860, Rbre950, Rbre960, Rbs860, Rbse950, or Rbse960) AND the installed firmware version is below the specified threshold (9.10.1.4 for Rbe970/Rbe971, 7.2.7.15 for the rest) AND the management interface is accessible from an untrusted local network segment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 7.2.7.15 / 9.10.1.4 or later
Fixed in 7.2.7.159.10.1.4
Interim mitigation

Apply available firmware updates from the router vendor; if no update exists, implement network segmentation or access control lists to restrict which local devices can communicate with the router's management interface.

Recommended fix Moderate confidence

Rbe970/Rbe971: upgrade to firmware 9.10.1.4 or later | Rbr860/Rbre950/Rbre960/Rbs860/Rbse950/Rbse960: upgrade to firmware 7.2.7.15 or later

  1. 1. Identify the specific Netgear router model from the affected list (Rbe970, Rbe971, Rbr860, Rbre950, Rbre960, Rbs860, Rbse950, or Rbse960)
  2. 2. Access the router's web management interface by entering the router's IP address in a web browser
  3. 3. Navigate to the firmware update section, typically found under 'Administration' or 'Advanced' settings
  4. 4. Check the current firmware version to confirm it is affected (Rbe970/Rbe971: < 9.10.1.4; all other models: < 7.2.7.15)
  5. 5. Download the appropriate firmware update from the official Netgear support website (support.netgear.com) for the specific model
  6. 6. In the router's web interface, upload the downloaded firmware file and initiate the update
  7. 7. Wait for the firmware update to complete - do not power off the router during this process
  8. 8. After the router restarts, verify the new firmware version is installed and the router is functioning normally
Caveat Firmware updates may temporarily disrupt network connectivity; ensure the update process is not interrupted

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Rbe970 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3088 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-3088 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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