Quick answers
- Is CVE-2026-17250 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-17250 being exploited in the wild.
- How severe is CVE-2026-17250?
- Informational severity, published 21 August 2026.
- Which products and versions are affected?
- TP-Link TL-MR6400 v7.
- Is there a fix for CVE-2026-17250?
- A patch was published on 2026-08-19: Firmware build 260714 (APAC) v7_1.3.0 released with security improvements Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-17250 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-17250?
- Check whether you run TP-Link TL-MR6400 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability is a stack-based buffer overflow in the firmware update functionality of TL-MR6400 v7, caused by unsafe processing of attacker-controlled metadata within firmware images. An authenticated attacker can craft a malicious firmware image with oversized metadata fields to trigger memory corruption during the update process. Successful exploitation results in arbitrary code execution on the affected device with the privileges of the firmware update process. The attack requires the attacker to have authentication credentials to initiate the firmware update, and a patch has been released (build 260714 as of 2026-08-19) that improves security.
Affected products
- TP-Link TL-MR6400 v7
Timeline
- 2026-08-21: disclosed
- 2026-08-19: patched: Firmware build 260714 (APAC) v7_1.3.0 released with security improvements