CVE-2026-15469

HIGHPre-NVD 7.77.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (29th 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 weekElevated
7.7EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • Public exploit or proof-of-concept code is available
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.7Exploit: Public PoCExposed 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).

The use of hard-coded cryptographic key vulnerability has been identified in the mesh functionality of Deco XE75 v3, XE5300 v3.6 and WE10800 v3.6.  A shared RSA-512 mesh group private key is present in the affected firmware and is used by the mesh protocol for node authentication.  An attacker who obtains the firmware image and has local network access may be able to authenticate as a mesh node without possessing a device-specific credential.

Successful exploitation may allow an unauthenticated adjacent attacker to impersonate a trusted mesh node and bypass mesh node authentication, which may permit unauthorized changes to device or mesh configuration, affecting confidentiality, integrity and availability.

CVSS v3
7.7
EG Score
7.7HIGHmedium confidence
EG Risk
51
EG Risk 51/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)
Severity77% × 45%
The EG Score, 7.7 of 10.
Exploitation40% × 40%
EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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.4%
EPSS %ILE
29th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

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 total (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)14 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 total (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 24, 2026

Last Modified

October 12, 2026

Advisory Details (5)

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

Security Advisory: Hard-coded Mesh Group Private Key in Deco XE75, XE5300, and WE10800 (CVE-2026-15469) | TP-Link

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

Vendor Advisories for CVE-2026-15469(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 18× in last 7d / 91× 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 171 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 71 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Publicly available exploits

(1 reference)

Public exploit code is referenced for this CVE (1 GitHub PoC). No release with the fix is confirmed, so defenders should restrict or isolate affected systems accordingly until one is applied.

  • GitHub PoCtony102741/CVE-2026-15469
    Published Aug 25, 2026

    CVE-2026-15469 — Hard-coded RSA-512 mesh group private key in TP-Link Deco XE75/XE5300/WE10800 (CWE-321). Advisory, analysis & PoC methodology (EN/KO).

    Open source ↗

Frequently asked(5)

What is CVE-2026-15469?
CVE-2026-15469 is a high-severity vulnerability; its CVE record was published on August 24, 2026. The use of hard-coded cryptographic key vulnerability has been identified in the mesh functionality of Deco XE75 v3, XE5300 v3.6 and WE10800 v3.6. A shared RSA-512 mesh group private key is present in the affected firmware and is used by the mesh protocol for node authentication. An attacker who…
When was the CVE record for CVE-2026-15469 published?
The CVE record for CVE-2026-15469 was published on August 24, 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 October 12, 2026; the record at its source may have been updated since.
Is CVE-2026-15469 actively exploited?
CVE-2026-15469 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (29th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-15469?
CVE-2026-15469 has a CVSS base score of 7.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-15469?
A fix for CVE-2026-15469 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-15469 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-15469?

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