CVE-2026-76784

HIGHPre-NVD 8.78.7
EchelonGraph scoreMEDIUM confidence

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

This high-severity CVE scores 8.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (8th 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
8.7EG
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.2%CVSS: 8.7Exploit: 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).

Multiple TP-Link Kasa smart home devices contain insufficient cryptographic protections in the local device communication protocol. An adjacent network attacker may intercept, replay or forge locally exchanged control messages, potentially resulting in unauthorized device control.

Successful exploitation could allow an attacker to manipulate the operational state of an affected device, resulting in unauthorized state changes, disruption of normal device functionality or a denial-of-service condition.

CVSS v3
8.7
EG Score
8.7HIGHmedium confidence
EG Risk
39
EG Risk 39/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)
Severity87% × 45%
The EG Score, 8.7 of 10.
Exploitation0.2% × 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 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.2%
EPSS %ILE
8th
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 26, 2026

Last Modified

August 28, 2026

Advisory Details (4)

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

Security Advisory: Insufficient Cryptographic Protections in Local Device Communication Protocol on Multiple Kasa Smart Home Devices (CVE-2026-76784) | TP-Link

https://www.tp-link.com/us/support/faq/5267/
Web page

Download Center | TP-Link

https://www.tp-link.com/us/support/download/
Web page

Download Center | TP-Link India

https://www.tp-link.com/in/support/download/
Web page

Download Center | TP-Link

https://www.tp-link.com/en/support/download/

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

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

Frequently asked(5)

What is CVE-2026-76784?
CVE-2026-76784 is a high-severity vulnerability; its CVE record was published on August 26, 2026. Multiple TP-Link Kasa smart home devices contain insufficient cryptographic protections in the local device communication protocol. An adjacent network attacker may intercept, replay or forge locally exchanged control messages, potentially resulting in unauthorized device control. Successful…
When was the CVE record for CVE-2026-76784 published?
The CVE record for CVE-2026-76784 was published on August 26, 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-76784 actively exploited?
CVE-2026-76784 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-76784?
CVE-2026-76784 has a CVSS base score of 8.7 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-76784?
A fix for CVE-2026-76784 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-76784 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2026-76784?

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