On this page (7 sections)
CVE-2026-129250 describes a buffer overflow in the Edimax BR6478ACV2 router, version 1.23. According to the GitHub Advisory Database entry, the affected element is the function formPPTPSetup in the file webs, and manipulating the pptpUserName argument leads to the overflow. The record says the attack can be started remotely and that the exploit has been disclosed publicly.
The vendor was contacted early about the disclosure and, per the same record, did not respond. No fixed version is listed. If you run this router at an office, a shop or a client site, or manage one for someone else, the sections below cover how to check exposure and what to do while no patch exists.
What happened
The record was published on November 14, 2026. It states that the function formPPTPSetup in the file webs of Edimax BR6478ACV2 1.23 contains a buffer overflow, reached by manipulating the pptpUserName argument. It says the attack can be initiated remotely and that the exploit has been publicly disclosed and may be used.
Only the original disclosure chain is available so far. The NVD entry repeats the same text, so it is not independent confirmation, and the GitHub entry is marked unreviewed. Treat the details as the researcher's claims as relayed by the databases, not as a vendor-verified analysis. The record does not describe how the exploit works, and this article does not speculate about it.
Technical details
A buffer overflow happens when a program writes data into a fixed-size memory area beyond its limits. Depending on the device, the result can be a crash or an attacker influencing how the program behaves. The CWE labels attached to this record, CWE-119 and CWE-120, are the general and classic forms of this problem.
The CVSS v4 metrics listed in the advisory are: network attack vector, low attack complexity, no attack requirements, low privileges required, no user interaction, and high impact on confidentiality, integrity and availability for both the vulnerable system and subsequent systems. The research does not describe what an exploit achieves in practice, so avoid assuming more than the scores state.
Who is affected
The only affected version named is Edimax BR6478ACV2 1.23. The research does not say whether other firmware versions or related models share the code, and it does not confirm that they are safe. If you run any version of this model, treat it as potentially affected until Edimax says otherwise.
Realistic exposure depends on where the management interface is reachable. This is general guidance rather than something the record states:
- Highest risk: routers with remote administration enabled or the admin interface otherwise exposed to the internet.
- Moderate risk: routers whose admin pages are reachable only from the local network, where an infected laptop or guest device could still reach them.
- Lower risk: routers with the admin interface restricted to a single trusted management machine.
Small businesses and home offices are the likely owners of this class of device. A router sits in front of everything else on the network, including point-of-sale systems and the servers behind it, so its exposure matters beyond the device itself.
How to check your exposure
Start by confirming whether you own the affected model and firmware, then check whether the admin interface is reachable from outside.
- Find the model and firmware version on the router's status or about page, or on its label. You are looking for BR6478ACV2 and version 1.23.
- Log in to the admin interface and check whether remote management or WAN-side administration is enabled. Turn it off if you do not need it.
- From a device outside your network (for example a phone on mobile data), try to open your public IP address on the router's admin port. If the login page loads, the interface is exposed.
- As general hygiene, review the router's account list and remove accounts you do not recognize.
If you also run websites behind this network, a read-only scan such as Webforta Scan can show what your public web presence exposes. It looks at your sites from the outside and does not inspect router firmware or detect this flaw, so your own external port review remains the more direct test for the router.
What to do now
No patch is listed and the vendor has not responded, so the goal is to shrink the attack surface and prepare for replacement.
- Identify every Edimax BR6478ACV2 on your networks, including those at client or branch locations.
- Disable remote or WAN-side administration so the web interface is not reachable from the internet.
- Restrict admin access to one trusted internal device or a dedicated management VLAN if the router supports it.
- Change the admin password to a long, unique one and remove unused accounts.
- If you do not use the PPTP VPN feature, leave it unconfigured.
- Check the Edimax support pages periodically for a firmware update; do not install firmware from unofficial sources.
- Plan a replacement with a supported router if no fix is released, particularly for business or payment-handling networks.
- Watch the router and your network's outbound traffic for unusual behavior, such as unexpected reboots or new outbound connections.
Detection and monitoring
Because exploitation in the wild is not confirmed, there are no published indicators of compromise to hunt for. Practical signs worth watching are unexpected router reboots or crashes, changed DNS or VPN settings, unfamiliar admin accounts, and unusual outbound connections from the router's address.
Keep an eye on what your public address exposes. Webforta Monitor can alert you to certificate and DNS changes for sites you run, which helps spot tampering on the network path, though it does not inspect router firmware or detect this flaw. For broader guidance on spotting a compromise, see how to check if a website is hacked.
What is still unknown
- Whether Edimax will publish a fix or an official advisory.
- Whether other BR6478ACV2 firmware versions or related models are affected.
- Whether the flaw is being exploited in the wild. The research does not confirm it, and the CVE is not in CISA KEV as of the record.
- The exact access needed to reach the vulnerable function.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
