Kasa EC70 v4
and EC71 v4 do not logically disable the production debug interface at the
firmware or chip level and do not lock the bootloader. 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 enter
a non-standard initialization path that exposes an unauthenticated root shell
during startup.
Successful exploitation may allow an
attacker with physical access to obtain root-level command access during device
startup, resulting in loss of confidentiality, integrity, and availability for
the affected device. Exploitation requires device disassembly, restoration of
the severed debug connection, and manipulation of the boot process.
0.2%(unchanged from 0.2% a week ago; 0.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 8th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-01. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-1191On-Chip Debug and Test Interface With Improper Access Control
Show the promptExplain CVE-2026-102370 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-102370?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-102370?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-102370 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.
Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.
Affected
tp-link systems inc.:kasa ec70 v4
tp-link systems inc.:kasa ec71 v4
Versions
From the CNA's record in the CVE List.
Product
Affected
TP-Link Systems Inc. Kasa EC70 V4
before 2.4.3 Build 20260902 rel.4511
TP-Link Systems Inc. Kasa EC71 V4
before 2.4.3 Build 20260902 rel.4511
Attack patterns (CAPEC)
CAPEC-1 Accessing Functionality Not Properly Constrained by ACLs Likelihood: High · Severity: High
CAPEC-180 Exploiting Incorrectly Configured Access Control Security Levels Likelihood: High · Severity: Medium
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.