dbcve.org
Rax120 FirmwareOperating system · Netgear

CVE-2026-0420

MEDIUM · 5.9 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 1.0.6.106 / 1.2.9.52 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable 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
An improper implementation of TLS certificate validation vulnerability found in NETGEAR's ReadyCloud client app which could allow an attacker to perform attacker-in-the-middle (MiTM) style attacks impacting the product's confidentiality. This vulnerability affects the listed NETGEAR models.

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

The ReadyCloud client app implements improper TLS certificate validation, likely failing to properly verify the certificate chain, hostname, or trust store. This allows an attacker positioned between the client and server to intercept communications by presenting a fraudulent certificate, compromising confidentiality of data in transit.

MitigationImplement proper TLS certificate validation including chain-of-trust verification, hostname validation, and rejection of expired or self-signed certificates. Ensure the application trusts only CA-signed certificates from trusted roots.

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
Rax120 FirmwareOperating system
Affected:< 1.2.9.52
Rax35 FirmwareOperating system
Affected:< 1.0.6.106
Rax38 FirmwareOperating system
Affected:< 1.0.6.106
Rax40 FirmwareOperating system
Affected:< 1.0.6.106

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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N

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 your Netgear router model
    Check the product label on the device or log into the router web interface and look for the model number (e.g., Rax120, Rax35, Rax38, or Rax40)
    Affected if The model is NOT one of Rax120, Rax35, Rax38, or Rax40 - you are not affected by this specific CVE
  2. Check your router firmware version
    Log into the router web interface, go to the Administration or Settings section, and locate the firmware version displayed. Compare it to the affected ranges: Rax120 < 1.2.9.52, Rax35/Rax38/Rax40 < 1.0.6.106
    Affected if Your firmware version is equal to or higher than the threshold for your model - you are NOT affected; if lower, proceed to next check
  3. Determine if ReadyCloud is enabled
    Log into the router web interface, navigate to ReadyCloud settings (usually under Remote Management or Storage settings), and check if the ReadyCloud service is turned on or configured
    Affected if ReadyCloud is disabled or not configured - you are NOT exposed to this vulnerability; if enabled, you ARE affected

You are affected by CVE-2026-0420 if you own an Rax120, Rax35, Rax38, or Rax40 router with firmware below the respective threshold AND have the ReadyCloud feature enabled.

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 1.0.6.106 / 1.2.9.52 or later
Fixed in 1.0.6.1061.2.9.52
Interim mitigation

Implement proper TLS certificate validation including chain-of-trust verification, hostname validation, and rejection of expired or self-signed certificates. Ensure the application trusts only CA-signed certificates from trusted roots.

Recommended fix Moderate confidence

Rax120: firmware 1.2.9.52 or later | Rax35/Rax38/Rax40: firmware 1.0.6.106 or later

  1. 1. Identify your exact NETGEAR router model (Rax120, Rax35, Rax38, or Rax40)
  2. 2. Visit the NETGEAR support website at kb.netgear.com and search for your model
  3. 3. Navigate to the Downloads or Firmware section for your model
  4. 4. Download the firmware version 1.2.9.52 (for Rax120) or 1.0.6.106 (for Rax35/Rax38/Rax40) - these are the minimum fixed versions
  5. 5. Access your router's web management interface by entering the router's IP address in a browser
  6. 6. Log in with your admin credentials
  7. 7. Navigate to the Advanced tab, then Administration, then Firmware Update (or similar path depending on exact model)
  8. 8. Select the option to upload manually and choose the downloaded firmware file
Caveat Standard firmware update - ensure you back up router configuration; some settings may need to be reapplied after update

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

Fix this in Rax120 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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