CVE-2026-76784

Insufficient Cryptographic Protections in Local Device Communication Protocol on Multiple TP-Link Kasa Smart Home Devices

HIGH
8.7
CVSS Score
Published: August 26, 2026 at 05:47 PM UTC
Updated: August 28, 2026 at 07:22 PM UTC
18 products affected across 1 vendorKasa KP125MKasa KP303Kasa ES20M

Using HS103P3 / HS103P4 v5 by TP-Link Systems Inc.?

Get instant alerts when new vulnerabilities affect HS103P3 / HS103P4 v5 - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.7
Exploit prediction
EPSS 0.2%
SSVC
No known exploit

Description

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.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

v < 1.1.1 Build 250908 Rel.112508
Affected range stops below 1.1.1 Build 250908 Rel.112508, so it looks safe — our inference, not a vendor statement
v < 1.0.3 Build 240529 Rel.145252
Affected range stops below 1.0.3 Build 240529 Rel.145252, so it looks safe — our inference, not a vendor statement
v < 1.1.1 Build 250908 Rel.112526
Affected range stops below 1.1.1 Build 250908 Rel.112526, so it looks safe — our inference, not a vendor statement
v < 1.1.0 Build 240415 Rel.171219
Affected range stops below 1.1.0 Build 240415 Rel.171219, so it looks safe — our inference, not a vendor statement
v < 1.1.6 Build 250522 Rel.210254
Affected range stops below 1.1.6 Build 250522 Rel.210254, so it looks safe — our inference, not a vendor statement
v < 1.1.3 Build 250908 Rel.112508
Affected range stops below 1.1.3 Build 250908 Rel.112508, so it looks safe — our inference, not a vendor statement
v < 1.0.3 Build 240723 Rel.192622
Affected range stops below 1.0.3 Build 240723 Rel.192622, so it looks safe — our inference, not a vendor statement
v < 1.0.3 Build 240723 Rel.192630v < 1.1.1 Build 240802 Rel.094131v < 1.1.1 Build 240802 Rel.094142
Affected range stops below 1.0.3 Build 240723 Rel.192630, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.1.1 Build 240802 Rel.094131, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.1.1 Build 240802 Rel.094142, so it looks safe — our inference, not a vendor statement
v < 1.1.2 Build 241220 Rel.171333
Affected range stops below 1.1.2 Build 241220 Rel.171333, so it looks safe — our inference, not a vendor statement
v < 1.1.1 Build 260710 Rel.082646
Affected range stops below 1.1.1 Build 260710 Rel.082646, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

SSVC — Action Prioritization

SSVCNo known exploitNot automatableTotal impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.7HIGHTPLink
Vector?

Quick Info

StatusAWAITING ANALYSIS
CWE
CWE-325

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card