Skip to content
Networks

CVE-2026-17250

8.5
High
EPSS 0.19%Aug 22, 2026

Authenticated buffer overflow in TL-MR6400 v7 firmware can enable remote code execution

common questions

Is CVE-2026-17250 being exploited?

Not confirmed. CVE-2026-17250 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.19% probability of exploitation in the next 30 days.

How severe is CVE-2026-17250?

CVE-2026-17250 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-17250?

Not known from our data. No patch reference has been recorded for CVE-2026-17250, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2026-17250 affect?

CVE-2026-17250 affects TP-Link TL-MR6400 v7 (firmware), Home/small-business routers using TL-MR6400 v7 firmware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-17250?

Install vendor firmware when released; meanwhile disable remote admin and restrict firmware uploads.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
TP-Link TL-MR6400 v7 (firmware)Home/small-business routers using TL-MR6400 v7 firmware
impact

Authenticated attacker can trigger stack buffer overflow to achieve arbitrary code execution, device takeover, persistent access, and traffic interception.

action required

Immediate action required

affected versions
TP-Link Systems Inc. TL-MR6400 v7.0
  • affected< 1.9.0 Build 260714

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free