CVE-2026-71914: VigorAP 1060C pre-auth UDP

CISO Take

CVE-2026-71914 is a critical (CVSS 9.8) pre-authentication command injection in the dray_apm component of multiple DrayTek VigorAP wireless access point models, triggered by a crafted UDP message sent after START_SPEED_TEST that lets a remote attacker execute arbitrary commands as root with no authentication or user interaction required. This is a networking-hardware vulnerability, not an AI/ML system flaw — it was almost certainly surfaced in this feed due to a naming collision between DrayTek's internal 'apm' component and the unrelated Python package 'apm' tracked in our AI supply-chain catalog, and there is no evidence any AI pipeline, model, or agent framework runs on or depends on VigorAP firmware. No EPSS score, CISA KEV listing, public exploit, or Nuclei template currently exists, so active exploitation is unconfirmed, but the pre-auth, zero-interaction profile makes it a prime target once a PoC surfaces. If VigorAP devices sit on your network (guest WiFi, branch offices, IoT segments), patch to the vendor's fixed firmware per the August 2026 DrayTek advisory and restrict UDP access to the AP management service in the meantime. This CVE should be excluded from AI-specific breaking alerts given the classification mismatch, while still being tracked in general vulnerability management.

Sources:NVDdraytek.comvulncheck.com

What is the risk?

CVSS 9.8 (critical) with AV:N/AC:L/PR:N/UI:N — network-exploitable, low complexity, no privileges or user interaction needed, full confidentiality/integrity/availability impact via root command execution. No EPSS percentile, CISA KEV listing, public exploit code, or Nuclei template currently exists, so real-world exploitation likelihood cannot be quantified from available exploitation signals; treat as high risk based on the CVSS profile alone until exploitation telemetry emerges. This risk exists entirely within DrayTek's WiFi AP firmware/hardware stack — it carries no AI/ML supply-chain, model, or pipeline risk and should not be weighted using this platform's AI-exposure risk model.

How does the attack unfold?

Network Reconnaissance

Attacker identifies a DrayTek VigorAP device reachable via UDP on the local network or an exposed management segment.

Crafted UDP Exploitation

Attacker sends a crafted UDP message spoofing a START_SPEED_TEST request to the dray_apm service, triggering unsanitized command injection (CWE-78).

Root Command Execution

The injected OS command executes with root privileges on the access point, giving the attacker full device control with no prior authentication.

Network Pivot / Persistence

Attacker uses the compromised AP to intercept WiFi traffic, establish persistence, or pivot toward other network segments.

Network Reconnaissance

Attacker identifies a DrayTek VigorAP device reachable via UDP on the local network or an exposed management segment.

Crafted UDP Exploitation

Attacker sends a crafted UDP message spoofing a START_SPEED_TEST request to the dray_apm service, triggering unsanitized command injection (CWE-78).

Root Command Execution

The injected OS command executes with root privileges on the access point, giving the attacker full device control with no prior authentication.

Network Pivot / Persistence

Attacker uses the compromised AP to intercept WiFi traffic, establish persistence, or pivot toward other network segments.

What systems are affected?

Package	Ecosystem	Vulnerable Range	Patched
VigorAP 1060C	—	—	No patch
VigorAP 903	—	—	No patch
VigorAP 906	—	—	No patch
VigorAP 912C	—	—	No patch
VigorAP 918R	—	—	No patch
VigorAP 960C	—	—	No patch

How severe is it?

CVSS 3.1

9.8 / 10

EPSS

2.6%

chance of exploitation in 30 days

Higher than 85% of all CVEs

Source: EPSS v3 — FIRST.org

Exploitation Status

No known exploitation

Sophistication

Trivial

What is the attack surface?

AVNetwork

ACLow

PRNone

UINone

SUnchanged

CHigh

IHigh

AHigh

What should I do?

1 step

Apply the DrayTek firmware update referenced in the vendor's August 2026 security advisory for all listed VigorAP models (918R, 960C, 1060C, 906, 912C, 903). Until patched, restrict or firewall UDP access to the dray_apm/AP-management service from untrusted or guest network segments, and avoid exposing VigorAP management interfaces directly to the internet. Monitor for anomalous UDP traffic containing START_SPEED_TEST-pattern payloads to affected devices, and audit whether any AI infrastructure (servers, GPU nodes) shares a network segment with vulnerable APs so lateral-movement exposure can be scoped. Because the AI-category tag on this CVE appears to be a false positive (keyword collision with the unrelated 'apm' pip package), flag it for reclassification in the enrichment pipeline rather than routing it through AI-specific alerting.

What does CISA's SSVC say?

DecisionTrack*

Exploitationnone

AutomatableYes

Technical Impacttotal

Source: CISA Vulnrichment (SSVC v2.0). Decision based on the CISA Coordinator decision tree.

How is it classified?

Code ExecutionPlugin

Which compliance frameworks are affected?

Compliance analysis pending. Sign in for full compliance mapping when available.

Frequently Asked Questions

What is CVE-2026-71914?

CVE-2026-71914 is a critical (CVSS 9.8) pre-authentication command injection in the dray_apm component of multiple DrayTek VigorAP wireless access point models, triggered by a crafted UDP message sent after START_SPEED_TEST that lets a remote attacker execute arbitrary commands as root with no authentication or user interaction required. This is a networking-hardware vulnerability, not an AI/ML system flaw — it was almost certainly surfaced in this feed due to a naming collision between DrayTek's internal 'apm' component and the unrelated Python package 'apm' tracked in our AI supply-chain catalog, and there is no evidence any AI pipeline, model, or agent framework runs on or depends on VigorAP firmware. No EPSS score, CISA KEV listing, public exploit, or Nuclei template currently exists, so active exploitation is unconfirmed, but the pre-auth, zero-interaction profile makes it a prime target once a PoC surfaces. If VigorAP devices sit on your network (guest WiFi, branch offices, IoT segments), patch to the vendor's fixed firmware per the August 2026 DrayTek advisory and restrict UDP access to the AP management service in the meantime. This CVE should be excluded from AI-specific breaking alerts given the classification mismatch, while still being tracked in general vulnerability management.

Is CVE-2026-71914 actively exploited?

No confirmed active exploitation of CVE-2026-71914 has been reported, but organizations should still patch proactively.

How to fix CVE-2026-71914?

Apply the DrayTek firmware update referenced in the vendor's August 2026 security advisory for all listed VigorAP models (918R, 960C, 1060C, 906, 912C, 903). Until patched, restrict or firewall UDP access to the dray_apm/AP-management service from untrusted or guest network segments, and avoid exposing VigorAP management interfaces directly to the internet. Monitor for anomalous UDP traffic containing START_SPEED_TEST-pattern payloads to affected devices, and audit whether any AI infrastructure (servers, GPU nodes) shares a network segment with vulnerable APs so lateral-movement exposure can be scoped. Because the AI-category tag on this CVE appears to be a false positive (keyword collision with the unrelated 'apm' pip package), flag it for reclassification in the enrichment pipeline rather than routing it through AI-specific alerting.

What is the CVSS score for CVE-2026-71914?

CVE-2026-71914 has a CVSS v3.1 base score of 9.8 (CRITICAL). The EPSS exploitation probability is 2.56%.

What are the technical details?

Original Advisory

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.

Exploitation Scenario

An attacker with network access to a VigorAP device (e.g., via guest WiFi, an exposed management VLAN, or after gaining an initial foothold elsewhere on the LAN) sends a crafted UDP packet mimicking a START_SPEED_TEST message to the dray_apm service; because the service fails to validate the message content before invoking a shell command (CWE-78), the attacker's injected command runs with root privileges. From there they gain full control of the access point — intercepting or manipulating WiFi traffic, pivoting deeper into the internal network, or using the AP as persistent infrastructure. No credentials, prior authentication, or user interaction are needed, so this is exploitable by any device that can reach the AP's UDP service.

Weaknesses (CWE)

CWE-78Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

CWE-78 — Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection'): The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component.

[Architecture and Design] If at all possible, use library calls rather than external processes to recreate the desired functionality.
[Architecture and Design, Operation] Run the code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by the software. OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows the software to specify restrictions on file operations. This may not be a feasible solution, and it only limits the impact to the operating system; the rest of the application may still be subject to compromise. Be careful to avoid CWE-243 and other weaknesses related to jails.

Source: MITRE CWE corpus.