Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain adjacent-network access during setup
-
DeliverySend crafted TDDP subtype 0x91 packet
-
ExploitOverflow fixed-size stack buffer in handler
-
ExecutionHijack control flow
-
ImpactExecute arbitrary code on device
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack buffer bounds checking
MITRE ATT&CK
1 technique 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 | Exploitation requires the attacker to be on the same adjacent/link-local network as the target (AV:A) - e.g., associated to the Wi-Fi or on the same L2 segment - and to reach the TDDPv2 service (/usr/bin/tddp) on a Deco M9 Plus v2. The critical limiting factor, encoded as AT:P, is that the vulnerable subtype 0x91 handler is reachable 'during the device setup phase,' so the attacker must act within that provisioning window rather than against a steady-state deployed device. No authentication is required (PR:N) and no user interaction is needed (UI:N), but the attacker must be able to craft a TDDP packet whose decrypted request data exceeds the fixed-size stack buffer. The adjacency requirement and setup-phase timing together substantially narrow realistic exploitation to a proximate attacker present during device onboarding. |
| Impact | This is a genuine but conditionally-gated risk. The CVSS 4.0 vector (AV:A/AC:L/AT:P/PR:N/UI:N) confirms an adjacent-network, unauthenticated vector with no user interaction, and high impact to confidentiality, integrity, and availability (VC:H/VI:H/VA:H), supporting RCE on an embedded network device - a serious outcome. However, two signals temper the real-world priority. First, AV:A (not AV:N) means the attacker must already be on the same adjacent/link-local network (e.g., Wi-Fi association or same L2 segment), not the open Internet. Second, AT:P (Attack Requirements: Present) encodes the description's key constraint: exploitation is tied to the 'device setup phase,' a transient window rather than a steady-state service. No EPSS score, KEV listing, or public POC was provided in the input, so there is no evidence of active or widespread exploitation (see exploitation status). The vendor-published CVSS of 7.7 (High) is consistent with the vector. Net: a legitimate High-severity embedded RCE worth patching promptly, but the adjacency requirement and setup-phase timing make opportunistic mass exploitation unlikely; realistic threat is a local/proximate attacker during provisioning. No conflicting signals were observed between the vector and the description - both point to adjacent, unauthenticated access during setup. |
| Exploit ScenarioDerived | An attacker on the same local network segment as a Deco M9 Plus v2 being provisioned sends a crafted TDDP subtype 0x91 packet whose decrypted payload exceeds the fixed-size stack buffer. The resulting stack-based buffer overflow (CWE-121) crashes the tddp service (denial of service) or is leveraged to execute arbitrary code on the device during its setup phase. No public exploit code was identified in the provided intelligence, so this scenario is inferred from the vulnerability description and CVSS vector rather than a demonstrated exploit. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Stack-based buffer overflow in the TDDPv2 service (/usr/bin/tddp) on TP-Link Deco M9 Plus v2 mesh units lets a network-adjacent, unauthenticated attacker crash the device or potentially execute arbitrary code, but only while the unit is in its setup/provisioning phase. A crafted TDDP request whose decrypted payload is longer than the fixed-size stack buffer used by the subtype 0x91 handler (CWE-121) triggers the overflow with no user interaction. No public exploit code has been identified at time of analysis and the flaw is not in CISA KEV; TP-Link has published fixed firmware. The risk is genuine but conditionally gated: the attacker must already sit on the same Wi-Fi/link-local segment during onboarding, which substantially narrows realistic exposure.
RemediationAI
Apply the vendor firmware update for Deco M9 Plus v2 from TP-Link's download pages (https://www.tp-link.com/en/support/download/deco-m9-plus/v2/#Firmware and https://www.tp-link.com/us/support/download/deco-m9-plus/v2/#Firmware) and follow advisory FAQ 5322 (https://www.tp-link.com/us/support/faq/5322/); patch availability is confirmed by the vendor, but no exact fixed build number is enumerated in the available data, so verify the minimum patched firmware version with TP-Link before considering the device remediated. Because the overflow is only reachable by an adjacent party while the unit is in its setup/provisioning phase, compensating controls should shrink that window rather than be treated as a patch substitute: perform initial setup and any post-factory-reset re-provisioning only on a trusted, controlled network (never on public, guest, or shared Wi-Fi), avoid leaving units sitting unprovisioned in setup mode on an untrusted segment, and use strong WPA2/WPA3 credentials plus SSID/VLAN segmentation so unauthorized clients cannot join the same L2 segment as the mesh node. Note that perimeter/port filtering of the TDDP service offers limited benefit against an attacker who must already be link-local adjacent, and that a factory reset re-enters setup mode and re-exposes the vulnerable subtype 0x91 code path until updated firmware is applied.
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 affected component is TP-Link's TDDPv2 debug/provisioning service, implemented by /usr/bin/tddp on the Deco M9 Plus v2 (CPE cpe:2.3:a:tp-link_systems_inc.:deco_m9_plus_v2:*:*:*:*:*:*:*:*). The root cause is a textbook CWE-121 stack-based buffer overflow: the subtype 0x91 handler decrypts an incoming TDDPv2 request and then copies the decrypted request data into a fixed-size stack buffer without first validating its length. Because the copied length is attacker-influenced, an adjacent, unauthenticated sender (PR:N, UI:N in the supplied CVSS 4.0 vector; our independent assessment scores it CVSS:3.1/AV:A/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:H) can overwrite adjacent stack memory, corrupt saved control data, and either crash the daemon (denial of service) or potentially redirect execution (arbitrary code execution). The CVSS 4.0 AT:P metric captures the key constraint that the vulnerable handler is only reachable during the device setup phase, while the high attack complexity and changed scope in the independent assessment reflect how adjacency plus setup-window timing gate the attack rather than any cryptographic barrier.
Know when Deco M9 Plus V2 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 unauthenticated access (AV:A/PR:N); AC:H reflects the setup-phase-only window (the 4.0 AT:P requirement); S:C and C/I/A:H for firmware-level code execution affecting the device.
Primary rating from Vendor (TPLink).
CVSS VectorVendor: TPLink
DescriptionCVE.org
A stack-based buffer overflow vulnerability exists in the TDDPv2 service (/usr/bin/tddp) on Deco M9 Plus due to insufficient validation of decrypted request data length before it is copied into a fixed-size stack buffer in the subtype 0x91 handler. Successful exploitation may allow an adjacent, unauthenticated attacker to cause a denial of service or achieve arbitrary code execution during the device setup phase through crafted TDDP packets.
Articles & Coverage 2
Executive ViewAI
TP-Link Deco M9 Plus v2 mesh units contain a high-severity stack buffer overflow in the TDDPv2 service that is exploitable only during the device's setup phase by a network-adjacent attacker. While no public exploit has been identified at time of analysis, successful exploitation could crash the device or potentially allow arbitrary code execution, disrupting network deployment. Leadership should prioritize patching affected units during onboarding and ensure provisioning occurs in trusted network segments.
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
EUVD-2026-91006
GHSA-fxpm-c4jc-x283
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB