Skip to content
eastbaycyber

CVE-2026-8775: Edimax BR-6428NS Buffer Overflow

CVSS · High
8.8
In CISA KEV
No
Published
Nov 16
Patch SLA & TriageVector: Network
7 days

High CVSS (8.8) vulnerability; prioritize internet-facing assets.

Exposure:
Control:
CVSS v3.1 Blast RadiusScore: 8.8
Decode Vector & Sub-Scores →
CVE explainers 9 min read
Security Research Desk Source-checked
Auto-checked against the official CVE record · Human-reviewed after publishing · Updated 2026-11-16
▲ Escalation ViewOne CVE, briefed at three altitudes — skim the Brief, weigh the Impact, or work the Runbook. The way a SOC actually reads it.
CISOBrief · 30-second brief

TL;DR - CVE-2026-8775 is a remote buffer overflow in Edimax BR-6428NS firmware 1.10. - The vulnerable endpoint is /goform/formL2TPSetup, using the L2TPUserName parameter. - NVD reports a public exploit; no vendor-fixed version was identified, so restrict management access immediately.

Summary

CVE-2026-8775 is an Edimax BR-6428NS vulnerability affecting firmware version 1.10. The flaw is in the router’s HTTP POST request handler for L2TP configuration. An attacker can manipulate the L2TPUserName parameter at /goform/formL2TPSetup to trigger a stack or heap buffer overflow. The available record confirms remote exploitability but does not establish the exact impact on every device configuration.

For broader defensive context, review our OWASP API Security Top 10 FAQ and MITRE ATT&CK glossary.

Field Value
CVE ID CVE-2026-8775
CVSS base score 8.8, High
CVSS vector Not available in the retrieved NVD response
Attack vector Network / remote
Authentication required Unknown
Affected product Edimax BR-6428NS
Affected version Firmware 1.10
Patch available No confirmed vendor patch or fixed version identified
Public exploit Yes, reported by NVD
CISA KEV status Not listed

The practical risk is highest when the router’s administrative web interface is reachable from an untrusted network, particularly the public Internet. The available material does not confirm whether WAN-side administration is enabled by default or whether authentication is required before reaching the vulnerable handler. Treat any Internet-reachable instance as exposed until its management-plane access is verified.

CVE-2026-8775 was published on May 18, 2026, and last modified in the supplied record on October 26, 2026. The vendor reportedly received notice but did not respond, and no authoritative fixed firmware release was identified.

Analyst’s Take: Restrict management access before attempting to validate the vulnerability. The public exploit report and lack of a confirmed fixed version make exposure control the clearest immediate action, while the incomplete CVSS data and unverified exploit details argue against assuming a consistent code-execution outcome.

AnalystImpact · assess the risk

Root Cause

The vulnerable component is the formL2TPSetup function in the router’s POST request handler. It processes the L2TPUserName parameter without adequately enforcing a safe length or otherwise safely handling attacker-controlled input. An oversized or specially constructed value can overwrite adjacent memory, producing a denial-of-service condition and potentially enabling code execution depending on firmware protections and exploit reliability.

The record identifies the weakness as a buffer overflow but does not provide source code, an exact overwrite offset, register-control details, or a reliable description of the corrupted memory region. It is therefore not possible to state from the available evidence whether exploitation consistently achieves arbitrary code execution. Defenders should treat the issue as potentially more serious than a simple crash because the affected service runs on a network appliance and a public exploit is reported.

Technical Notes

The vulnerable request path and parameter are:

POST /goform/formL2TPSetup
L2TPUserName=<attacker-controlled value>

A safe investigation should avoid sending exploit payloads to production equipment. Use configuration review, passive HTTP telemetry, and controlled validation in an isolated lab instead. Do not reproduce the overflow against an Internet-facing router without explicit authorization and a recovery plan.

Who’s Exposed

The confirmed affected product is the Edimax BR-6428NS wireless router running firmware 1.10. The supplied NVD information does not identify additional BR-6428NS firmware versions, related Edimax models, or a broader vulnerable version range. Administrators should not assume that every firmware release or similarly named Edimax product is affected based solely on this CVE.

Vendor Product Confirmed affected version
Edimax BR-6428NS Firmware 1.10

Exposure depends on network placement and management configuration. A device may be vulnerable even if its WAN interface is filtered: an attacker who compromises an internal host, gains access to a guest network, or connects to an inadequately segmented wireless network may still reach the management interface. The available record does not confirm whether authentication is required, so organizations should not rely on authentication as the primary control.

Inventory teams should identify BR-6428NS devices by model and firmware version rather than by CVE scanning alone. Older embedded devices may not expose a reliable software inventory interface, and network scanners may miss management pages protected by access controls. Confirm the firmware version through an authorized local administration path or documented asset records.

Severity Breakdown

NVD assigns CVE-2026-8775 a CVSS base score of 8.8, rated High. The score indicates substantial risk, consistent with a remotely reachable memory-safety vulnerability. However, the complete CVSS vector was not returned in the retrieved NVD API response. The individual metrics, including privileges required, user interaction, and confidentiality, integrity, and availability impacts, must therefore be treated as unknown rather than inferred.

The known characteristics support prioritization: the vulnerable handler is network-accessible through the device’s web-management service, and a public exploit is reported. The absence of a confirmed KEV listing does not reduce the technical severity. It means only that CISA did not list the CVE in its Known Exploited Vulnerabilities catalog at the time of the supplied lookup.

CVSS component Available assessment
Base score 8.8
Severity High
Attack vector Remote/network, as described by the record
Attack complexity Unknown from supplied data
Privileges required Unknown
User interaction Unknown
Scope Unknown
Confidentiality impact Unknown
Integrity impact Unknown
Availability impact Unknown

For operational prioritization, place Internet-exposed devices ahead of isolated units. Devices used as edge gateways deserve particular attention because compromise could provide traffic interception, configuration tampering, persistence, or access to internal networks, although those outcomes are not confirmed specifically for this CVE.

Exploitation Status

A public exploit is reported. The NVD description states that “the exploit has been published and may be used,” which is sufficient to classify public exploit availability as reported. The supplied research did not identify a directly accessible GitHub proof-of-concept repository or independently reproduce the exploit. The primary disclosure reference is hosted on Notion, but the retrieved page returned the application shell rather than the underlying technical content.

Confirmed exploitation in the wild has not been established from the available sources. CVE-2026-8775 is not listed in CISA KEV, so it should not be described as a CISA-confirmed actively exploited vulnerability. That status is not proof that exploitation is absent. Public exploit availability, limited vendor support, and the presence of vulnerable management interfaces still justify urgent defensive action.

Question Current answer
Is a public exploit reported? Yes, according to NVD
Is a directly verified PoC available from the supplied sources? Not confirmed
Is exploitation confirmed in the wild? Not established
Is the CVE in CISA KEV? No
Is ransomware use reported? Not reported in the supplied material

Sources

The primary technical source is the NVD record for CVE-2026-8775. It identifies Edimax BR-6428NS firmware 1.10, the formL2TPSetup handler, the /goform/formL2TPSetup endpoint, the L2TPUserName parameter, a CVSS score of 8.8, and reported public exploit availability.

The supplied sources do not provide a complete CVSS vector, a confirmed fixed firmware version, a directly verified GitHub PoC, authentication requirements, default WAN exposure, or evidence of exploitation in the wild. Those gaps should remain explicit in vulnerability records and risk decisions rather than being filled with assumptions.

This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.

ResponderRunbook · act now

Detection Guidance

Detection should focus on access to the router’s web-management interface and unusual POST requests to the vulnerable path. Network telemetry may show requests containing unusually long L2TPUserName values, malformed form data, repeated requests, or a router restart shortly after the request. Because many small routers have limited logging, the absence of an application log entry does not demonstrate that exploitation did not occur.

Review firewall, reverse-proxy, wireless-controller, and network-monitoring logs for external or untrusted clients reaching the router’s administration address. Correlate suspicious requests with device symptoms such as unexpected reboots, lost configuration, changed DNS settings, new administrative accounts, or altered L2TP settings. Preserve available logs before rebooting or resetting a potentially compromised device.

Technical Notes

A generic web or proxy log search can identify the affected path:

grep -E 'POST[[:space:]]+/goform/formL2TPSetup([?[:space:]]|$)' \
  /var/log/nginx/access.log /var/log/httpd/access_log 2>/dev/null

For systems forwarding HTTP telemetry to a SIEM, a conceptual query is:

http.method = "POST"
AND url.path = "/goform/formL2TPSetup"
AND network.client.ip NOT IN trusted_management_ranges

If request-body logging is enabled and legally appropriate, investigate unusually large values for L2TPUserName:

url.path = "/goform/formL2TPSetup"
AND form.L2TPUserName.length > expected_l2tp_username_limit

No authoritative length threshold was provided for this product. Do not treat an arbitrary threshold as a vendor-defined detection rule. Use normal device behavior from a controlled baseline and alert on significant deviations. Also monitor for an HTTP service interruption or reboot within a short period after a suspicious request.

Remediation Steps

No confirmed vendor patch or fixed firmware version was identified in the supplied sources. The available information identifies firmware 1.10 as affected but does not specify an upgrade target. Administrators should check Edimax support channels directly for a firmware release that explicitly addresses CVE-2026-8775 or the formL2TPSetup buffer overflow. Do not claim that an unverified newer firmware version is a fix.

Until a vendor-supported fix is confirmed, remove the administrative interface from untrusted networks. Disable remote administration if it is not required, restrict access to a dedicated management VLAN, and permit only approved administrator IP addresses. If the device cannot be patched and must remain exposed, replacement or isolation is the safest long-term action.

Technical Notes

A representative firewall policy should deny untrusted access to the router management address while allowing only the management network. Replace the example addresses and interface names with values from the local environment:

# Example Linux firewall policy protecting a management address.
# Validate the device's actual management port before deployment.
sudo iptables -A INPUT -p tcp -d 192.0.2.1 --dport 80 \
  ! -s 198.51.100.0/24 -j DROP
sudo iptables -A INPUT -p tcp -d 192.0.2.1 --dport 443 \
  ! -s 198.51.100.0/24 -j DROP

If Edimax publishes a confirmed fixed firmware image, upgrade using the vendor’s documented procedure rather than an unofficial image. Record the current firmware, configuration backup, image checksum where available, and post-upgrade version:

1. Confirm the model is BR-6428NS and record current firmware 1.10.
2. Obtain firmware only from an authenticated Edimax support source.
3. Verify the release notes explicitly address CVE-2026-8775 or the L2TP setup handler.
4. Back up configuration and preserve relevant logs.
5. Upgrade during a controlled maintenance window.
6. Confirm the reported firmware version after reboot.
7. Recheck that WAN-side management remains disabled or restricted.

Do not send a crafted oversized L2TPUserName value as a production validation test. If compromise is suspected, disconnect or isolate the router, preserve logs and configuration evidence, rotate credentials managed through the device, and replace the unit if firmware provenance or integrity cannot be established.

Choosing a tool? Pricing and head-to-head guides

Last verified: 2026-11-16

Disclaimer: This article may contain affiliate links. We earn a commission on qualifying purchases at no extra cost to you.