CVE-2026-129250: Contain Edimax BR-6478AC V2 management access
If you manage an Edimax BR-6478AC V2 running firmware 1.23, restrict access to its management interface while you confirm a remediation path with Edimax. VulDB’s CNA record for CVE-2026-129250 identifies that version as affected and rates the flaw Critical at CVSS 3.1 9.9. The record names no fixed firmware version.
The buffer overflow affects pptpUserName processing in the formPPTPSetup function of webs. The CNA scores it as network reachable with low privileges required (PR:L), so describing it as unauthenticated would be inaccurate. Its timeline dates the advisory to November 13, 2026; the CVE record was published on November 14 at 11:30:19 UTC. Only 1.23 is explicitly listed. Other firmware versions are not established as safe or affected by that record.
Read the severity and exploit claims carefully
The NVD API record also lists CVSS 3.1 9.9 Critical. Its base vector is CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H.
There is a v4.0 reporting difference: the CNA JSON stores 9.4 Critical in its baseScore field, while NVD stores 8.6 High for the imported VulDB v4.0 metric. Both include the threat metric E:P; NVD attributes the metric to cna@vuldb.com, not a separate NIST assessment. Keep the source and CVSS version with any score copied into a ticket.
VulDB says a public exploit exists and that the vendor did not respond to its disclosure contact. Those are the CNA’s statements. The reviewed records do not establish active exploitation. FIRST defines E:P as proof-of-concept exploit maturity, distinct from the attacked category. No exploit was run for this article.
Check the router and reduce exposure
Confirm the exact model and hardware revision from the device label. Then use an authorized local management connection to record the firmware version. The BR-6478AC V2 manual documents the current version under Administration, Upgrade, and the Remote Access control under Administration. Menu availability varies with operating mode.
For a 1.23 device, the following are containment recommendations, not a vendor-confirmed fix for this CVE:
- Disable Remote Access if it is enabled. Plan the change from a trusted local connection so you do not lock yourself out, and follow the interface’s save/restart prompts.
- Restrict management access to trusted administrators. Where your network supports it, block access from guest and other untrusted segments using the network equipment that enforces those boundaries.
- Review who knows the management password and replace default or reused credentials. A strong password does not repair the overflow.
After the change, verify the saved settings and ordinary management reachability from authorized test locations. A login page still reachable from an untrusted network needs investigation; a failed connection alone does not prove that the firmware is patched. Do not send oversized usernames or other exploit requests to a working router.
The function name does not establish that switching off PPTP makes the management handler unreachable. Avoid changing the WAN connection type as a guessed workaround: it can interrupt internet service.
Confirm a supported firmware path
Ask Edimax for a firmware build that explicitly addresses CVE-2026-129250 for the BR-6478AC V2 and your region. No fixed version was verified on November 14, 2026. An older download or a newer version number alone is insufficient evidence of a fix.
Edimax’s EOS announcement says web-UI OTA updates ended in November 2024, with exceptions for two named smart-plug models. Do not rely on the router’s automatic update check. Use the vendor’s download/support channel to verify availability. That announcement lists BR-6478AC V3 among discontinued models; it does not establish V2’s support status.
If Edimax supplies a confirmed update, follow its instructions for the exact hardware, preserve the recovery information you need, and use a wired connection without interrupting power. Check the installed version and management restrictions afterward. If no supported fix is available and you cannot adequately restrict access, plan to replace or remove the device. Updating a Linux workstation does not update the router’s firmware.
Inspect the public record from Linux
This example downloads advisory metadata, not router configuration. It needs Bash, curl and Python 3. Start in a scratch directory and keep the same terminal session for cleanup. Stop if directory creation or changing into it fails.
advisory_dir=$(mktemp -d ./edimax-advisory.XXXXXX) &&
cd -- "$advisory_dir"Save this as inspect-edimax-record.py inside that directory:
import json
from pathlib import Path
import sys
response = json.loads(Path(sys.argv[1]).read_text(encoding="utf-8"))
records = response["vulnerabilities"]
if len(records) != 1 or records[0]["cve"]["id"] != "CVE-2026-129250":
raise SystemExit("Expected exactly CVE-2026-129250")
cve = records[0]["cve"]
print("CVE:", cve["id"])
for source in cve["affected"]:
for product in source["affectedData"]:
for version in product["versions"]:
if version["status"] == "affected":
print(f"Listed affected: {product['product']} {version['version']}")
for key in ("cvssMetricV31", "cvssMetricV40"):
metric = next(m for m in cve["metrics"][key] if m["source"] == "cna@vuldb.com")
score = metric["cvssData"]
print(f"NVD CVSS {score['version']}: {score['baseScore']} {score['baseSeverity']}")
if key == "cvssMetricV40":
print("Exploit maturity:", score["exploitMaturity"])
print("Metadata only; no router was inspected.")Download the record and run the helper:
curl --fail --silent --show-error --max-time 30 \
'https://services.nvd.nist.gov/rest/json/cves/2.0?cveId=CVE-2026-129250' \
--output edimax-nvd.json &&
python3 inspect-edimax-record.py edimax-nvd.jsonActual output on Debian 13 with Python 3.12.14, November 14, 2026:
CVE: CVE-2026-129250
Listed affected: BR6478ACV2 1.23
NVD CVSS 3.1: 9.9 CRITICAL
NVD CVSS 4.0: 8.6 HIGH
Exploit maturity: PROOF_OF_CONCEPT
Metadata only; no router was inspected.NVD can revise the live record, so retain its download date with your ticket. This helper does not check your installed firmware, exposure or patch status. Remove only the example files and scratch directory when finished:
rm -- inspect-edimax-record.py edimax-nvd.json &&
cd .. &&
rmdir -- "$advisory_dir" &&
unset advisory_dirOnly the public-record download and local parser were executed. No Edimax hardware, firmware update or containment change was tested.
This post was created with assistance from AI.