CVE-2022-27646
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 · uneditedThis vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of NETGEAR R6700v3 1.0.4.120_10.0.91 routers. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the circled daemon. A crafted circleinfo.txt file can trigger an overflow of a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-15879.
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 confidenceStack-based buffer overflow in the circled daemon of NETGEAR R6700v3 routers (firmware 1.0.4.120_10.0.91) allows network-adjacent attackers to execute arbitrary code as root via a crafted circleinfo.txt file. The authentication mechanism can be bypassed, enabling unauthenticated attackers to trigger the overflow.
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< 1.0.4.126< 1.0.4.126< 1.3.3.148< 1.0.11.134< 1.3.3.148< 1.0.5.84< 1.4.3.88< 1.0.4.84CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify router modelCheck the device label on the router or log into the router web interface (usually at 192.168.1.1) and look for the model number displayed on the administration pageAffected if Model is one of the following: R6400, R6700, R6900p, R7000, R7000p, R7850, R7960p, or R8000
-
Check installed firmware versionIn the router web interface, go to the Administration or Firmware Update section and note the current firmware version stringAffected if The firmware version is lower than the threshold for your model: R6400/R6700 below 1.0.4.126, R6900p/R7000p below 1.3.3.148, R7000 below 1.0.11.134, R7850 below 1.0.5.84, R7960p below 1.4.3.88, or R8000 below 1.0.4.84
-
Verify circled daemon presenceIf you have CLI access via telnet or SSH to the router, run 'ps' to list running processes and look for 'circled' or 'circle' in the process listAffected if The circled daemon is running on the device (the vulnerability exists in this daemon)
-
Assess network exposureCheck your router WAN interface settings and determine if remote management (HTTP/HTTPS management access from WAN) is enabled. Also check if the router is directly exposed to untrusted networksAffected if Remote management is enabled or the router is accessible from untrusted network segments, allowing network-adjacent attackers to reach the circled daemon
You are affected if you have a listed Netgear router model running firmware version below the threshold for your model and the circled daemon is accessible from an untrusted network.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.0.4.841.0.4.1261.0.5.84
Apply the vendor-supplied NETGEAR firmware update when available. Until then, restrict network access to trusted users and disable any unnecessary remote management features.
R6400: 1.0.4.126 | R6700: 1.0.4.126 | R6900p: 1.3.3.148 | R7000: 1.0.11.134 | R7000p: 1.3.3.148 | R7850: 1.0.5.84 | R7960p: 1.4.3.88 | R8000: 1.0.4.84
- 1. Identify your NETGEAR router model from the affected list (R6400, R6700, R6900p, R7000, R7000p, R7850, R7960p, or R8000)
- 2. Visit the official NETGEAR support page at kb.netgear.com and navigate to your router model's download area
- 3. Download the firmware version that matches or exceeds: R6400: 1.0.4.126 | R6700: 1.0.4.126 | R6900p: 1.3.3.148 | R7000: 1.0.11.134 | R7000p: 1.3.3.148 | R7850: 1.0.5.84 | R7960p: 1.4.3.88 | R8000: 1.0.4.84
- 4. Access your router's web management interface by entering its IP address in a web browser
- 5. Navigate to the Administration or Advanced settings section
- 6. Locate the Firmware Update option and select the downloaded firmware file
- 7. Wait for the upload and installation to complete - do not power off the router during this process
- 8. After the router reboots, verify the new firmware version in the router's status page
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation6.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,080.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-27646 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2022-27646 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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