dbcve.org
Rbe370 FirmwareOperating system · Netgear

CVE-2026-0409

MEDIUM · 6.4 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 12.1.2.7 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable

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
A NETGEAR security issue that could allow an attacker with ability to intercept and tamper with traffic between the router and the Internet to run commands on your device when the device administrator performs certain specific management actions. This issue affects NETGEAR Orbi 370 series devices before V12.1.2.7.

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

A vulnerability in NETGEAR Orbi 370 series routers before firmware V12.1.2.7 allows an attacker with man-in-the-middle capability between the router and the Internet to execute arbitrary commands on the device when the administrator performs specific management actions. The attack requires traffic interception/tampering capability.

MitigationUpdate NETGEAR Orbi 370 series devices to firmware version V12.1.2.7 or later. Restrict physical and network access to prevent unauthorized traffic interception.

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
Rbe370 FirmwareOperating system
Affected:< 12.1.2.7
Rbe371 FirmwareOperating system
Affected:< 12.1.2.7
Rbe372 FirmwareOperating system
Affected:< 12.1.2.7
Rbe374 FirmwareOperating system
Affected:< 12.1.2.7

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
Network
Complexity
High
Privileges
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:R/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 checks

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

  1. Identify router model
    Check the product label on the router or log into the web management interface to confirm the exact model number (Rbe370, Rbe371, Rbe372, or Rbe374)
    Affected if Model is one of Rbe370, Rbe371, Rbe372, or Rbe374
  2. Locate firmware version
    Log into the router web administration panel (typically at 192.168.1.1 or orbilogin.com) and navigate to the Administration or Firmware Update section to find the currently installed firmware version
    Affected if Router is one of the affected models and firmware version is displayed
  3. Compare firmware version to threshold
    Compare the installed firmware version number to 12.1.2.7 - note that versions are compared numerically (e.g., 12.1.2.6, 10.5.3.1, and any version below 12.1.2.7 are considered lower)
    Affected if Installed firmware version is less than 12.1.2.7 (for example, 12.1.2.6, 12.1.1.5, etc.)
  4. Verify management traffic exposure
    This vulnerability requires an attacker to intercept traffic between the router and the internet - consider whether the router is deployed on a network where MITM attacks are plausible (shared networks, compromised ISP infrastructure, etc.)
    Affected if Router is on an affected model with vulnerable firmware AND network position allows traffic interception

You are affected if your NETGEAR Orbi router is model Rbe370, Rbe371, Rbe372, or Rbe374 and is running firmware version lower than 12.1.2.7, especially if managed over untrusted networks.

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 12.1.2.7 or later
Fixed in 12.1.2.7
Interim mitigation

Update NETGEAR Orbi 370 series devices to firmware version V12.1.2.7 or later. Restrict physical and network access to prevent unauthorized traffic interception.

Recommended fix High confidence

Firmware version 12.1.2.7

  1. Log in to the NETGEAR Orbi router web interface by navigating to routerlogin.net or routerlogin.com
  2. Navigate to the Administration or Settings section
  3. Look for Firmware Update or Router Update option
  4. Check for available updates - the router should show version 12.1.2.7 or later as the fixed release
  5. If automatic update is available, click to download and install the update
  6. If manual update is required, download the firmware from the official NETGEAR support website (kb.netgear.com or www.netgear.com) for your specific model (Rbe370, Rbe371, Rbe372, or Rbe374)
  7. Upload the firmware file through the web interface and wait for the update to complete
  8. After reboot, verify the firmware version shows 12.1.2.7 or later

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

Fix this in Rbe370 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0409 — 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-0409 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