CVE-2026-8775
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 · uneditedA flaw has been found in Edimax BR-6428NS 1.10. This affects the function formL2TPSetup of the file /goform/formL2TPSetup of the component POST Request Handler. This manipulation of the argument L2TPUserName causes buffer overflow. It is possible to initiate the attack remotely. The exploit has been published and may be used. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceA buffer overflow vulnerability exists in the formL2TPSetup function of Edimax BR-6428NS firmware version 1.10, specifically in the POST request handler for /goform/formL2TPSetup. The vulnerability is triggered by insufficient bounds checking on the L2TPUserName parameter, allowing remote attackers to overflow a buffer and potentially execute arbitrary code.
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
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm device model and firmware versionAccess the router's web administration interface and navigate to Status or System Info page to view the firmware version. Alternatively, check the label on the device or the admin interface footer for version information.Affected if The device is an Edimax BR-6428NS running firmware version 1.10.
-
Verify L2TP VPN functionality is enabledLog into the router's web interface and navigate to the L2TP VPN setup page (typically under VPN or Advanced settings). Check whether L2TP is configured or enabled.Affected if L2TP VPN functionality is enabled or configured on the device, as the vulnerability exists in the formL2TPSetup handler.
-
Confirm web interface accessibilityCheck if the router's web administrative interface (HTTP/HTTPS on port 80 or 443) is reachable from the network. This vulnerability is exploitable via the web interface.Affected if The router's web interface is accessible from untrusted networks, increasing exposure to remote exploitation.
-
Inspect web server logs for anomalous L2TP requestsIf the router supports logging or if external logging is configured, review access logs for POST requests to /formL2TPSetup with unusually long L2TPUserName parameters.
The device is affected if it is an Edimax BR-6428NS running firmware 1.10 with L2TP VPN functionality enabled and the web interface is accessible.
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 dataRestrict network access to the router's administrative web interface (port 80/443) to trusted IPs only, and disable L2TP functionality if not required, as no vendor patch is available.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8775 — 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-8775 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