CVE-2026-27846
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 · uneditedDue to missing authentication, a user with physical access to the device can misuse the mesh functionality for adding a new mesh device to the network to gain access to sensitive information, including the password for admin access to the web interface and the Wi-Fi passwords.This issue affects MR9600: 1.0.4.205530; MX4200: 1.0.13.210200.
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 confidenceThis is an authentication bypass vulnerability in the mesh device pairing functionality of specific router models. A physically proximate attacker can exploit the lack of authentication during mesh device addition to inject a rogue mesh node, which then exposes stored credentials including the administrator web interface password and Wi-Fi network keys.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify router model and firmware versionAccess the router's web administration interface or check the device label/specified admin page to determine the exact model number and current firmware version.Affected if The model and version fall within the vendor's affected product list but specific ranges are not provided in this CVE data.
-
Verify mesh functionality statusLog into the router administration panel and navigate to the mesh or wireless settings section. Look for options labeled 'mesh', 'mesh network', 'EasyMesh', or 'Wi-Fi Easy Mesh' and check whether they are enabled.Affected if Mesh functionality is turned ON - the vulnerability only applies when mesh pairing is active.
-
Inspect connected mesh nodesIn the router's admin interface, locate the device list, mesh node list, or client table. Enumerate all mesh nodes or range extenders currently associated with the network.Affected if Any unknown, unrecognized, or suspiciously named mesh nodes are present in the list.
-
Review device association logsCheck the router's system logs, event logs, or security logs for any recent 'mesh node added', 'device connected', or 'pairing' events, especially those occurring without admin notification or at unexpected times.Affected if Log entries indicate mesh devices were added without your explicit authorization.
-
Examine admin password and Wi-Fi credential exposureIf a rogue mesh node is suspected, check whether the administrator web interface password or Wi-Fi network keys have been changed or are no longer functional, or if new wireless networks have appeared.Affected if Credentials have changed unexpectedly or unauthorized wireless networks are now visible.
A user is affected if they use an affected router model/version with mesh functionality enabled and either detect unauthorized mesh nodes or discover compromised credentials.
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.
From vendor dataApply vendor firmware updates when released. Until then, restrict physical access to the router and monitor for unauthorized mesh device associations. Consider disabling mesh functionality if not required.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27846 — 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-2026-27846 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