Authenticated memory corruption via L2TPUserName handling
Published May 18, 2026 · Updated May 18, 2026
Buffer overflow in Edimax BR-6428nS 1.10 allows remote authenticated users to corrupt memory through a crafted L2TP setup request. The formL2TPSetup handler at /goform/formL2TPSetup processes an oversized L2TPUserName POST value without enforcing the destination buffer's bounds. Low-privileged access to the management interface is required, and public evidence does not establish whether corruption yields a crash or code execution.
Summary
What happened
Buffer overflow in Edimax BR-6428nS 1.10 allows remote authenticated users to corrupt memory through a crafted L2TP setup request. The formL2TPSetup handler at /goform/formL2TPSetup processes an oversized L2TPUserName POST value without enforcing the destination buffer's bounds. Low-privileged access to the management interface is required, and public evidence does not establish whether corruption yields a crash or code execution.
The record
- CVE
- CVE-2026-8775
- Published
- May 18, 2026
- Updated
- May 18, 2026
- Vendor
- Edimax Technology Co., Ltd.
- Product
- BR-6428nS
- Classifications
- CWE-119, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 18, 2026CVE publishedPublication date reported by the CVE source.
- May 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.10
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- VulDB submission 811530proof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo