CVE-2026-17251

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week
7.1EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.5%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

A NULL pointer dereference vulnerability exists in the HTTP request parsing functionality of  TL-MR6400 v7. An unauthenticated remote attacker can trigger the vulnerability by sending a specially crafted HTTP request containing a malformed session cookie header.

Successful exploitation may cause the HTTP service process to crash, resulting in a denial-of-service condition and temporary loss of management or CGI functionality until service recovery.

CVSS v3
7.1
EG Score
7.1HIGHmedium confidence
EG Risk
32
EG Risk 32/100

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 (value × EchelonGraph’s weight)
Severity71% × 45%
The EG Score, 7.1 of 10.
Exploitation0.5% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
0.5%
EPSS %ILE
38th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

August 21, 2026

Last Modified

August 28, 2026

Advisory Details (3)

Auto-updated Aug 21, 2026
Fix referenced — no release confirmed yet.
Web page

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/
Web page

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

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

Vendor Advisories for CVE-2026-17251(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 / 96× 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 183 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 83 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Frequently asked(5)

What is CVE-2026-17251?
CVE-2026-17251 is a high-severity vulnerability; its CVE record was published on August 21, 2026. A NULL pointer dereference vulnerability exists in the HTTP request parsing functionality of TL-MR6400 v7. An unauthenticated remote attacker can trigger the vulnerability by sending a specially crafted HTTP request containing a malformed session cookie header. Successful exploitation may cause the…
When was the CVE record for CVE-2026-17251 published?
The CVE record for CVE-2026-17251 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-17251 actively exploited?
CVE-2026-17251 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.5% probability of exploitation in the next 30 days (38th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-17251?
CVE-2026-17251 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-17251?
A fix for CVE-2026-17251 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation. The vendor advisories EchelonGraph has for CVE-2026-17251 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-17251?

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