dbcve.org
R6260 FirmwareOperating system · Netgear

CVE-2025-12942

HIGH · 7.5 CVSS v3.1 Published 2025-11-11
Fix available
A fix is available. Upgrade to 1.1.0.86 or later.
See remediation →
80/100
Remediation priority · High
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
Improper Input Validation vulnerability in NETGEAR R6260 and NETGEAR R6850 allows unauthenticated attackers connected to LAN with ability to perform MiTM attacks and control over DNS Server to perform command execution.This issue affects R6260: through 1.1.0.86; R6850: through 1.1.0.86.

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

Improper input validation in the DNS handling functionality of NETGEAR R6260 and R6850 routers (firmware through 1.1.0.86) allows unauthenticated attackers on the LAN who can perform man-in-the-middle attacks and control the DNS server to inject malicious input leading to arbitrary command execution on the router.

MitigationApply vendor firmware updates when available. Until then, minimize LAN exposure, disable unnecessary remote management features, and monitor for unauthorized DNS configuration changes.

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
R6260 FirmwareOperating system
Affected:< 1.1.0.86
R6850 FirmwareOperating system
Affected:< 1.1.0.86

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

CVSS:3.1/AV:A/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 checks

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

  1. Identify router model
    Access the router web interface or check the device label to confirm the exact model number is Netgear R6260 or R6850
    Affected if Model is not R6260 or R6850, then the device is not affected by this specific CVE
  2. Check firmware version
    In the router web interface, navigate to the Administration or Firmware Upgrade section to view the current firmware version, or use the command line if available
    Affected if Firmware version is 1.1.0.86 or higher, then the vulnerability has been patched
  3. Verify DNS configuration access
    In the router web interface, go to Internet/WAN settings or Basic Setup to check if DNS server settings are configurable (either manual DNS entries or DNS relay options)
    Affected if DNS settings are not accessible or not configurable, the specific attack vector may not be available but the underlying code flaw may still exist in older firmware
  4. Assess LAN exposure
    Review network segmentation, guest WiFi settings, and any bridged devices to determine if untrusted devices could access the LAN and potentially perform man-in-the-middle attacks on DNS traffic
    Affected if Untrusted or unknown devices have direct LAN access, an attacker could potentially reach the DNS handling code

The router is affected if it is a Netgear R6260 or R6850 model running firmware version below 1.1.0.86, with accessible DNS configuration settings and sufficient LAN exposure for an attacker to control DNS responses.

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.1.0.86 or later
Fixed in 1.1.0.86
Interim mitigation

Apply vendor firmware updates when available. Until then, minimize LAN exposure, disable unnecessary remote management features, and monitor for unauthorized DNS configuration changes.

Recommended fix Moderate confidence

R6260 and R6850 firmware version 1.1.0.86 or later

  1. 1. Visit the official NETGEAR support website (support.netgear.com) and navigate to the download page for your specific router model (R6260 or R6850).
  2. 2. Locate the firmware version 1.1.0.86 or later for your router model.
  3. 3. Download the firmware file from NETGEAR's official source.
  4. 4. Access your router's web management interface by entering the router's IP address in a web browser.
  5. 5. Log into the router administration panel with administrator credentials.
  6. 6. Navigate to the Firmware Update or Administration section of the router settings.
  7. 7. Upload and apply the downloaded firmware file (1.1.0.86 or later).
  8. 8. Wait for the firmware upgrade to complete and the router to reboot.
Caveat Firmware upgrades may reset router configuration to defaults; backup settings before upgrading if custom configurations exist

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

Fix this in R6260 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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