Skip to main content

TP-Link TL-MR6400 EUVDEUVD-2026-64006

| CVE-2026-17250 HIGH
Stack-based Buffer Overflow (CWE-121)
2026-08-21 TPLink GHSA-82fj-885j-3xg6
8.5
CVSS 4.0 · Vendor: TPLink
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain admin credentials via default/reused passwords
  2. Delivery
    Gain adjacent network access to management interface
  3. Exploit
    Craft firmware image with oversized malicious metadata
  4. Execution
    Upload crafted image via firmware update function
  5. Persist
    Stack buffer overflow overwrites return address
  6. Impact
    Execute 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 all of the following conditions simultaneously: (1) the attacker must have high-privilege (administrative) credentials to the TL-MR6400 v7 management interface - confirmed by PR:H in the CVSS 4.0 vector; (2) the attacker must have adjacent network access to reach the device management interface - confirmed by AV:A, meaning direct internet exploitation is not possible without prior network access or pivoting; (3) the target device must be running TL-MR6400 hardware version 7 firmware prior to the patched release. Exploitation is limited by the need for admin-level authentication (eliminating unauthenticated remote attackers) and network adjacency (eliminating arbitrary internet-based actors). Defenders who enforce unique strong admin credentials and segment device management interfaces substantially reduce realistic exploitability regardless of patch status.

Impact

The CVSS 4.0 score of 8.5 (AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H) reflects high impact across all three CIA pillars but is substantially constrained by the adjacent network vector and high privilege requirement. An attacker must already hold administrative credentials on the device - a significant prerequisite that limits the realistic threat to insider threats, credential-reuse scenarios, or cases where default credentials remain unchanged. The AV:A metric means the management interface must be reachable from the attacker's network segment, ruling out opportunistic internet-scale exploitation without additional pivoting. No EPSS data was provided, and the absence of a KEV listing or known public POC further reduces immediate risk. The combination of PR:H and AV:A makes this a high-severity but relatively contained vulnerability in practice; organizations with properly segmented networks and enforced credential hygiene face lower exposure than the raw score implies. The primary risk population is deployments where admin passwords are default or shared and where the device management interface is reachable from untrusted segments.

Exploit ScenarioDerived

An attacker who has obtained administrative credentials to the TL-MR6400 v7 management interface - whether via default credentials, credential reuse, or prior compromise - connects from an adjacent network segment and uploads a specially crafted firmware image. The firmware metadata fields are copied into a fixed-size stack buffer without bounds checking, overwriting the return address with attacker-controlled data. Upon function return, execution is redirected to attacker-supplied shellcode or a ROP chain, yielding code execution with the privileges of the firmware update process on the embedded device.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 21, 2026

Stack-based buffer overflow in TP-Link TL-MR6400 v7 firmware update functionality enables an authenticated, adjacent-network attacker to achieve arbitrary code execution on the affected device. The flaw (CWE-121) arises from unsafe parsing of attacker-controlled metadata embedded in a firmware image, leading to memory corruption at the stack level. No public exploit or CISA KEV listing has been identified at time of analysis; exploitation is further constrained by requirements for high-privilege access (PR:H) and network adjacency (AV:A).

RemediationAI

Apply the patched firmware released by TP-Link for the TL-MR6400 v7, available at https://www.tp-link.com/en/support/download/tl-mr6400/v7/#Firmware. While the exact patched firmware version number is not specified in the provided data, the vendor advisory at https://www.tp-link.com/us/support/faq/5259/ should identify the minimum safe version. As compensating controls pending patching: restrict access to the device's web management interface to a dedicated, trusted management VLAN or host-based allowlist, eliminating access from untrusted segments (this directly negates the AV:A attack vector); change default administrator credentials to a strong, unique password (this negates the PR:H prerequisite in credential-reuse scenarios); and disable remote management features if not actively required. Note that restricting management access may impact legitimate administrative workflows and should be coordinated with network teams.

Affected VersionsENISA

TL-MR6400 v7.0 0 <1.9.0 Build 260714

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

CWE-121 (Stack-based Buffer Overflow) describes a condition where a program writes beyond the bounds of a stack-allocated buffer, overwriting return addresses or control data. In this case, the TL-MR6400 v7 firmware update routine fails to validate the length or content of metadata fields within an attacker-supplied firmware image before copying them onto the stack. The CPE string (cpe:2.3:a:tp-link_systems_inc.:tl-mr6400_v7.0:*:*:*:*:*:*:*:*) confirms the specific affected model is version 7.0 of TP-Link's TL-MR6400, a consumer/SMB 4G LTE router. Because this is embedded firmware running on a MIPS or ARM-based SoC, exploit mitigations such as ASLR and stack canaries may be absent or weakly implemented, potentially lowering exploitation complexity once the prerequisite access conditions are met.

Know when Tl Mr6400 V7 0 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

Vendor (TPLink) PRIMARY 8.5 HIGH
CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 6.8 MEDIUM

Adjacent network vector and high privileges required match CVSS 4.0 input; full CIA impact reflects arbitrary code execution on the device with no scope change.

3.1 AV:A/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
4.0 AV:A/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (TPLink).

CVSS VectorVendor: TPLink

Attack Vector
Adjacent
Attack Complexity
Low
Attack Requirements
None
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

A stack-based buffer overflow vulnerability exists in the firmware update functionality of TL-MR6400 v7 due to unsafe processing of attacker-controlled metadata within a firmware image.

Successful exploitation may allow an authenticated attacker to trigger memory corruption and execute arbitrary code on the affected device.

Executive ViewAI

Why It Matters

TP-Link TL-MR6400 v7 routers contain a firmware vulnerability enabling attackers with administrative access on the local network to execute arbitrary code and potentially compromise network infrastructure. Organizations should prioritize patching these devices to protect network security and prevent unauthorized network control.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 91% exploitable
Prevalence
Low
niche consumer/SMB 4G LTE router, limited enterprise deployment footprint
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Controlled
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

42
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +42
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy