Answer in brief
CVE-2026-102370 records a Medium severity (CVSS 5.4) vulnerability in Physical UART Access Leading to an Unauthenticated Root Shell in TP-Link Kasa EC70 and EC71. The current sources do not mark it as known exploited. The current feed maps TP-Link Systems Inc./Kasa EC70 V4 (generic), TP-Link Systems Inc./Kasa EC71 V4 (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 5.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps TP-Link Systems Inc./Kasa EC70 V4 (generic), TP-Link Systems Inc./Kasa EC71 V4 (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| TP-Link Systems Inc./Kasa EC70 V4generic | >=0 <2.4.3 Build 20260902 rel.4511 | 2.4.3 Build 20260902 rel.4511, 2.4.3 |
| TP-Link Systems Inc./Kasa EC71 V4generic | >=0 <2.4.3 Build 20260902 rel.4511 | 2.4.3 Build 20260902 rel.4511, 2.4.3 |
Published upstream
Oct 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 1, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 1, 2026
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.
Quoted source text, attributed separately from HOL analysis.