Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent-network/LAN position
-
DeliverySend crafted setProductVer to TDDPv2 (tddp)
-
ExploitInject OS command via command handler
-
ExecutionAwait or trigger device reboot
-
PersistCommand runs as root at boot
-
ImpactFull router compromise and LAN pivot
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization OS command sanitization, avoid shell exec
MITRE ATT&CK
2 techniques across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | The attacker must occupy an adjacent-network position (same L2 segment - wired LAN, Wi-Fi including guest networks, or wireless range) to reach the TDDPv2 service (/usr/bin/tddp) on the Archer AX90 V1; no authentication is required (PR:N). Exploitation targets the setProductVer command handler to inject OS commands, but the injected command executes as root during device boot - so a reboot must occur or be induced for the payload to run (the AT:P attack requirement). Principal limiting factors: adjacent-network access only (not internet-exploitable), the boot-timing dependency, and applicability restricted to Archer AX90 V1; a fixed firmware release is available from the vendor. |
| Impact | This is a credible, above-average-priority issue for affected fleets, but not an internet-wide emergency. The CVSS 4.0 vector (AV:A/AC:L/AT:P/PR:N/UI:N) confirms an unauthenticated (PR:N) attacker limited to the adjacent network (AV:A) - i.e. the same LAN/Wi-Fi/L2 segment, NOT remote internet access - and the AT:P attack requirement reflects a real timing dependency: the injected command executes during device boot, so exploitation hinges on a reboot occurring. Technical impact is severe (VC:H/VI:H/VA:H, command execution as root = full device compromise), with modest spillover to subsequent systems (SC:L/SI:L/SA:L), consistent with a compromised router pivoting onto the LAN. No EPSS score, no CISA KEV listing, and no public POC were provided, so there is no evidence of active exploitation or weaponization; the realistic signal is 'high-impact but access- and timing-constrained.' Compared across signals: impact is high, but the adjacent-network precondition plus the boot-timing requirement materially lower real-world exploitability versus a true network-facing RCE. A vendor patch is available, which is the decisive mitigating factor. Key missing data to note: no EPSS, no KEV, no POC status, and the SSVC/automatable determination is not provided. |
| Exploit ScenarioDerived | An attacker who has gained a foothold on the local network (e.g. a guest Wi-Fi client, a compromised IoT device, or someone within wireless range) sends a crafted setProductVer request to the TDDPv2 service (/usr/bin/tddp) on an Archer AX90 V1. The injected OS command is stored and executed with root privileges during the next device boot, yielding full control of the router. No public exploit code was identified at time of analysis, and successful execution depends on a reboot occurring. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Command injection in the TDDPv2 service (/usr/bin/tddp) on TP-Link Archer AX90 V1 routers allows an unauthenticated attacker who is already positioned on the same adjacent network layer - wired LAN, Wi-Fi, or guest network - to inject operating system commands through the setProductVer command handler, which then run as root. The injected payload is executed during device boot, so the attacker must wait for or induce a reboot, and the device is not exploitable over the internet; a fixed firmware release is available from the vendor. Analysis found no public exploit code (no public exploit identified at time of analysis) and the issue is not in CISA KEV, so this is assessed as a credible but above-average-priority fleet risk rather than an internet-wide emergency.
RemediationAI
Patch available per vendor advisory: install the latest Archer AX90 V1 firmware from the TP-Link download pages at https://www.tp-link.com/us/support/download/archer-ax90/v1/#Firmware (or the /en/ equivalent), following the guidance in https://www.tp-link.com/us/support/faq/5323/; no exact fixed version string is supplied in the available data, so verify the release notes on those pages before upgrading. Until the upgrade is applied, the most effective compensating control is to remove the adjacent-network exposure the attack depends on: isolate guest Wi-Fi as internet-only with client isolation enabled, segment or disable untrusted wired LAN ports, and keep the device out of reach of untrusted users within wireless range, since any host on the same L2 segment (PR:N, no credentials needed) can reach the TDDPv2 handler. Blocking or filtering the TDDPv2 service traffic at the LAN/Wi-Fi boundary reduces exposure but will break vendor debug and management tooling that relies on the protocol, so test before deploying broadly. Because the injected command only runs at boot (AT:P), aggressive patch-outs are not an acceptable substitute for patching, and monitoring for unexpected reboots or unusual outbound behavior after a restart is a useful detection backstop rather than a fix.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The TDDP (TP-Link Device Debug Protocol) v2 daemon ships as /usr/bin/tddp on the Archer AX90 V1 and exposes command handlers over a Layer 2 adjacent network segment without requiring credentials (CVSS PR:N). The root-cause class is CWE-78 (improper neutralization of special elements used in an OS command), here manifested in the setProductVer handler, which passes externally influenced product-version input into a shell invocation as root; the injected commands therefore execute with full device privileges during the boot sequence. The provided CPE, cpe:2.3:a:tp-link_systems_inc.:archer_ax90_v1:*:*:*:*:*:*:*:*, scopes the issue to the V1 hardware revision across firmware versions. The reported CVSS 4.0 vector (7.7, AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H) and the independent assessment (CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) agree on adjacent-network attack vector, no authentication, and high confidentiality/integrity/availability impact, and both capture the boot-timing prerequisite (AT:P / AC:H) that makes a reboot necessary before injected commands run.
Know when Archer Ax90 V1 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L
Adjacent-network and unauthenticated (AV:A/PR:N); AC:H reflects the boot-timing precondition; S:C and C/I/A:H because root command execution compromises the router and the LAN behind it.
Primary rating from Vendor (TPLink).
CVSS VectorVendor: TPLink
DescriptionCVE.org
A command injection vulnerability exists in the TDDPv2 service (/usr/bin/tddp) on Archer AX90 V1. An unauthenticated adjacent-network attacker can exploit the setProductVer command handler to execute arbitrary operating system commands as root during device boot.
Successful exploitation may result in complete device compromise through arbitrary command execution with root privileges.
Articles & Coverage 2
Executive ViewAI
TP-Link Archer AX90 V1 routers carry a high-severity command-injection issue that can give an attacker on the same wired, Wi-Fi, or guest network root-level control of the device, creating a persistent foothold that may survive reboots until remediated. Because these routers often sit at the edge of small-office, branch, or home-office environments and may carry business or guest traffic, an exploited device could expose local network activity or be used as a pivot point. A vendor firmware patch is available, and no public exploit identified at time of analysis; leadership should prioritize fleet-wide firmware verification and update.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
OS command injection occurs when an application passes unsanitized user input directly into system shell commands.
EUVD-2026-91040
GHSA-gjhm-8mvw-7r24
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB