Skip to main content
VulnerabilityPublished

CVE-2026-102370: TP-Link Systems Kasa EC70 V4 · On-Chip debug and test interface with improper access control

Affects TP-Link Systems Kasa EC70 V4Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium : upgrade to 2.4.3 Build 20260902 rel.4511 when convenient.

Data as of 15 Nov 2026, 20:25 UTC

CVSS 4.0 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.1% chance of exploitation in 30 days – higher than 7% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 2.4.3 Build 20260902 rel.4511
CVSS:4.0/AV:P/AC:L/AT:P/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.

What to do

Upgrade Kasa to 2.4.3 Build 20260902 rel.4511.

Affected software

ProductAffectedFixed in
TP-Link Systems Inc.Kasa EC70 V4Affected
  • =0
Fixed in
  • 2.4.3 Build 20260902 rel.4511
TP-Link Systems Inc.Kasa EC71 V4Affected
  • =0
Fixed in
  • 2.4.3 Build 20260902 rel.4511

AI-suggested

Mitigation requires physical security controls to prevent unauthorized physical access to the device. Monitor vendor advisories for any future firmware updates or bootloader locking mechanisms that address this issue.

Description

The TP-Link Kasa EC70 V4 and EC71 V4 devices have an improper access control vulnerability in their on-chip debug and test interface. The production debug interface is not logically disabled at the firmware or chip level, and the bootloader is not locked. Although the debug traces are physically severed during manufacturing, an attacker with physical access can restore the connection, interrupt the boot process, and manipulate boot parameters to gain an unauthenticated root shell during startup. This allows root-level command access, compromising the device's confidentiality, integrity, and availability. Exploitation requires physical device disassembly and manipulation of hardware and boot processes.

References

Community reviews

Loading reviews…