CVE-2026-17250

HIGHPre-NVD 8.58.5—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.5 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3% (20th percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Trending — 3 sources updated this week
8.5EG
EchelonGraph verdictPlan mitigationSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 8.5Exploit: None knownExposed services: Not assessed

No fix is confirmed yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for the fix.

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.

CVSS v3
8.5
EG Score
8.5HIGHmedium confidence
EG Risk
38
EG Risk 38/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity85% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

August 21, 2026

Last Modified

August 28, 2026

Advisory Details (3)

Auto-updated Aug 21, 2026
No fix on record yet.
generic

Security Advisory: Multiple Vulnerabilities in TL-MR6400 (CVE-2026-17250, CVE-2026-17251 & CVE-2026-17252) | TP-Link

https://www.tp-link.com/us/support/faq/5259/
generic

下載 TL-MR6400 | TP-Link 台灣地區

https://www.tp-link.com/tw/support/download/tl-mr6400/v7/#Firmware

Vendor Advisories for CVE-2026-17250(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 20× in last 7d / 101× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 184 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 84 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  2. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  3. 2026-10-09 05:53 UTCEG score recompute
  4. 2026-10-09 05:53 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  5. 2026-10-08 17:11 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  6. 2026-10-08 04:55 UTCEG score recompute
  7. 2026-10-08 04:55 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  8. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  9. 2026-10-07 06:36 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  10. 2026-10-06 19:21 UTCEG score recompute
  11. 2026-10-06 19:21 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  12. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  13. 2026-10-06 07:49 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  14. 2026-10-05 19:27 UTCEG score recompute
  15. 2026-10-05 19:27 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  16. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  17. 2026-10-05 08:02 UTCEG score recompute
  18. 2026-10-05 08:02 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  19. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  20. 2026-10-04 20:48 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  21. 2026-10-04 06:36 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  22. 2026-10-03 19:24 UTCEG score recompute
  23. 2026-10-03 19:23 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  24. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  25. 2026-10-03 07:04 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
Show 75 more
  1. 2026-10-02 19:51 UTCEG score recompute
  2. 2026-10-02 19:51 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  3. 2026-10-02 08:38 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  4. 2026-10-01 21:25 UTCEG score recompute
  5. 2026-10-01 21:25 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  6. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.3% · 20th percentile
  7. 2026-10-01 07:41 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  8. 2026-09-30 20:28 UTCEG score recompute
  9. 2026-09-30 20:28 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  10. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  11. 2026-09-30 07:53 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  12. 2026-09-29 16:11 UTCEG score recompute
  13. 2026-09-29 16:11 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  14. 2026-09-29 15:20 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  15. 2026-09-29 00:25 UTCEG score recompute
  16. 2026-09-29 00:25 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  17. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  18. 2026-09-28 13:12 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  19. 2026-09-28 01:59 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  20. 2026-09-27 14:40 UTCEG score recompute
  21. 2026-09-27 14:40 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  22. 2026-09-27 13:47 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  23. 2026-09-27 02:29 UTCEG score recompute
  24. 2026-09-27 02:29 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  25. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.3% · 19th percentile
  26. 2026-09-25 17:07 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  27. 2026-09-25 04:08 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  28. 2026-09-24 16:55 UTCEG score recompute
  29. 2026-09-24 16:55 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  30. 2026-09-24 05:28 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  31. 2026-09-23 18:14 UTCEG score recompute
  32. 2026-09-23 18:14 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  33. 2026-09-23 06:56 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  34. 2026-09-22 19:43 UTCEG score recompute
  35. 2026-09-22 19:43 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  36. 2026-09-22 07:23 UTCEG score recompute
  37. 2026-09-22 07:23 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  38. 2026-09-21 20:09 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  39. 2026-09-21 08:56 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  40. 2026-09-20 21:25 UTCEG score recompute
  41. 2026-09-20 21:25 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  42. 2026-09-20 10:12 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  43. 2026-09-19 22:59 UTCEG score recompute
  44. 2026-09-19 22:59 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  45. 2026-09-19 11:45 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  46. 2026-09-19 00:20 UTCEG score recompute
  47. 2026-09-19 00:20 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  48. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  49. 2026-09-18 13:07 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  50. 2026-09-18 01:54 UTCEG score recompute
  51. 2026-09-18 01:54 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  52. 2026-09-17 14:41 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  53. 2026-09-17 03:26 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  54. 2026-09-16 16:02 UTCEG score recompute
  55. 2026-09-16 16:02 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  56. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  57. 2026-09-16 05:14 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  58. 2026-09-16 04:49 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  59. 2026-09-15 17:36 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  60. 2026-09-15 06:19 UTCEG score recompute
  61. 2026-09-15 06:19 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  62. 2026-09-14 19:06 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  63. 2026-09-14 07:33 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  64. 2026-09-13 20:20 UTCEG score recompute
  65. 2026-09-13 20:20 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  66. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  67. 2026-09-13 09:06 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  68. 2026-09-12 21:54 UTCEG score recompute
  69. 2026-09-12 21:54 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  70. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 9th percentile
  71. 2026-09-12 10:40 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  72. 2026-09-11 23:26 UTCEG score recompute
  73. 2026-09-11 23:26 UTCGHSA enrichmentGHSA-82fj-885j-3xg6 · GitHub severity HIGH
  74. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 8th percentile
  75. 2026-09-11 12:06 UTCEG score recompute

Frequently asked(5)

What is CVE-2026-17250?
CVE-2026-17250 is a high vulnerability published on August 21, 2026. 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…
When was the CVE record for CVE-2026-17250 published?
The CVE record for CVE-2026-17250 was published on August 21, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of August 28, 2026; the record at its source may have been updated since.
Is CVE-2026-17250 actively exploited?
CVE-2026-17250 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-17250?
CVE-2026-17250 has a CVSS base score of 8.5 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-17250?
No fix for CVE-2026-17250 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2026-17250 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-17250

Explore →

Is Your Infrastructure Affected by CVE-2026-17250?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.