CVE-2026-71914: DrayTek VigorAP Multiple Models Pre-Authentication OS Command Injection via dray_apm
Multiple DrayTek VigorAP models contain a command injection vulnerability in the dray_apm component. The vulnerability is caused by insufficient validation of UDP message content after START_SPEED_TEST before command execution. A remote attacker can trigger this vulnerability via a crafted message to execute arbitrary commands with root privileges.
Security readout for executives and security teams
Plain-English summary
A network attacker could potentially take full control of a vulnerable DrayTek VigorAP without credentials or user interaction. Successful exploitation could expose wireless traffic, alter network configuration, disrupt connectivity, or provide a foothold for broader compromise. The supplied data does not clearly identify affected firmware versions.
Executive priority
Treat this as an urgent asset-identification and remediation issue because compromise requires no credentials and may grant root control. Prioritize devices reachable from untrusted networks. Leadership should track completion, but the uncertain firmware scope means teams must confirm exposure against DrayTek's advisory before declaring individual devices vulnerable.
Technical view
CVE-2026-71914 is a pre-authentication OS command injection in the dray_apm component. Insufficient validation of UDP content following START_SPEED_TEST can permit crafted network messages to execute arbitrary commands as root. CVSS 3.1 rates it 9.8: network-accessible, low complexity, no privileges, and high confidentiality, integrity, and availability impact.
Likely exposure
Potential exposure includes the named VigorAP 918R, 960C, 1060C, 906, 912C, and 903 models when the relevant UDP service is attacker-reachable. However, the supplied affected-product records list version "0" with a default status of unaffected, so they do not establish a reliable vulnerable firmware range.
Exploitation context
The flaw is remotely triggerable without authentication or user interaction and provides root-level command execution, making successful attacks potentially severe. The source bundle marks it as absent from KEV and provides no cited evidence of active exploitation. This does not prove exploitation is not occurring.
Researcher notes
CWE-78 and the CVSS vector support the command-injection and remote pre-authentication assessment. The supplied structured affected data is internally unclear: six models are named, yet version "0" and defaultStatus "unaffected" do not define vulnerable releases. No exploit availability, indicators of compromise, fixed versions, or active campaigns are established by the supplied evidence.
Mitigation direction
Check DrayTek's advisory for model-specific fixed firmware and upgrade instructions.
Restrict untrusted UDP access to affected access points where operationally feasible.
Segment access points from sensitive systems and tightly limit their permitted network communications.
If updates are unavailable, seek vendor guidance and consider temporarily isolating potentially vulnerable devices.
Validation and detection
Inventory the named VigorAP models and record their exact firmware versions.
Compare each firmware version against DrayTek's current advisory; do not rely on the ambiguous version "0" records.
Confirm whether untrusted networks can reach the relevant UDP service.
After remediation, verify installed firmware and retest network restrictions without sending malicious payloads.
Review available device and network logs for unexplained configuration changes or unexpected privileged activity.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-78: Command execution behavior lookup
Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
3Timeline events
1ADP providers
3Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-78 · source CWE mapping
Improper Neutralization of Special Elements used in an OS Command
Improper Neutralization of Special Elements used in an OS Command represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.