Authenticated code execution via firmware metadata overflow
Published Aug 21, 2026 · Updated Aug 25, 2026
Stack-based buffer overflow in TP-Link TL-MR6400 V7 before 1.9.0 Build 260714 allows remote authenticated users to execute code. The firmware update handler processes attacker-controlled image metadata without enforcing the stack buffer's bounds. Exploitation requires high-privilege access from an adjacent network and a crafted firmware upload, and successful corruption permits code execution on the router.
Summary
What happened
Stack-based buffer overflow in TP-Link TL-MR6400 V7 before 1.9.0 Build 260714 allows remote authenticated users to execute code. The firmware update handler processes attacker-controlled image metadata without enforcing the stack buffer's bounds. Exploitation requires high-privilege access from an adjacent network and a crafted firmware upload, and successful corruption permits code execution on the router.
The record
- CVE
- CVE-2026-17250
- Published
- Aug 21, 2026
- Updated
- Aug 25, 2026
- Vendor
- TP-Link Systems Inc.
- Product
- TL-MR6400
- Classifications
- CWE-121, CAPEC-100, T1190
- Attack vector
- adjacent
- Privileges
- admin
Timeline
How it unfolded
- Aug 21, 2026CVE publishedPublication date reported by the CVE source.
- Aug 25, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.9.0 Build 260714
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo