Authenticated memory corruption via PPPoE username overflow
Published May 30, 2026 · Updated May 30, 2026
Stack-based buffer overflow in Edimax BR-6478AC 1.23 allows remote authenticated users to corrupt memory through PPPoE setup. The formPPPoESetup POST handler accepts a manipulated pppUserName argument that overruns a stack-based buffer. Low-privileged management access is required; exploitation can disrupt the router process, but published sources do not establish code execution.
Summary
What happened
Stack-based buffer overflow in Edimax BR-6478AC 1.23 allows remote authenticated users to corrupt memory through PPPoE setup. The formPPPoESetup POST handler accepts a manipulated pppUserName argument that overruns a stack-based buffer. Low-privileged management access is required; exploitation can disrupt the router process, but published sources do not establish code execution.
The record
- CVE
- CVE-2026-10125
- Published
- May 30, 2026
- Updated
- May 30, 2026
- Vendor
- Edimax Technology Co., Ltd.
- Product
- BR-6478AC
- Classifications
- CWE-119, CWE-121, T1190
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- May 30, 2026CVE publishedPublication date reported by the CVE source.
- May 30, 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.23
What conditions does exploitation require?
What is affected?
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
- EDIMAX BR6478ACV2 formPPPoESetup proof of conceptproof 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