dbcve.org
R6260 FirmwareOperating system · Netgear

CVE-2021-34979

HIGH · 8.8 CVSS v3.1 Published 2022-01-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
93/100
Remediation priority · Urgent
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
This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of NETGEAR R6260 1.1.0.78_1.0.1 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of SOAP requests. When parsing the SOAPAction header, the process does not properly validate the length of user-supplied data prior to copying it to a fixed-length buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-13512.

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 · high confidence

Buffer overflow vulnerability in NETGEAR R6260 router firmware 1.1.0.78_1.0.1. The router's SOAP request handler fails to validate the length of the SOAPAction header before copying user-supplied data into a fixed-size buffer. An unauthenticated attacker on the adjacent network can trigger this overflow to achieve arbitrary code execution with root privileges.

MitigationSince NETGEAR R6260 is end-of-life with no available patch, restrict management interface access via network segmentation, disable UPnP, and replace with a supported router model. If continued use is required, isolate the device behind a strict firewall and monitor for compromise.

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.78_1.0.1

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/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 the router model
    Check the device label on the router or query the device via SNMP, UPnP, or HTTP banner for model identification (look for R6260 in device info)
    Affected if Device is a NETGEAR R6260
  2. Check the firmware version
    Access the router admin web interface (typically at 192.168.1.1) and navigate to Settings > Router Status or Administration > Firmware Update to view the installed firmware version; alternatively, query the device via telnet/SSH if enabled
    Affected if Firmware version is 1.1.0.78_1.0.1
  3. Verify SOAP service exposure
    Perform a port scan of the router (ports 80, 443, 5555, 1900) to detect if UPnP/SSDP or SOAP services are listening; check if port 5555 (common UPnP port) or HTTP/HTTPS is exposed to the local network
    Affected if SOAP/UPnP service is accessible on the local network adjacent to the router
  4. Confirm network accessibility
    From a host on the same network segment as the router, attempt to reach the router's management interface (HTTP/HTTPS) and SOAP endpoints; verify if authentication is required and if the SOAPAction header can be sent without credentials
    Affected if Router management or SOAP endpoints are reachable from an unauthenticated adjacent network host without requiring credentials

If the device is a NETGEAR R6260 running firmware 1.1.0.78_1.0.1 and the SOAP/UPnP service is exposed to the adjacent network, the environment is affected by this vulnerability.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since NETGEAR R6260 is end-of-life with no available patch, restrict management interface access via network segmentation, disable UPnP, and replace with a supported router model. If continued use is required, isolate the device behind a strict firewall and monitor for compromise.

Fix this in R6260 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 help mitigating

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-2021-34979 — 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-2021-34979 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