Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
5.4
CVE-2026-102370: TP-Link Kasa EC70/EC71 can give root shell via UART
CVE-2026-102370 · published 1 month ago
Summary
The EC70 and EC71 smart plugs let a person who opens the device reconnect a hidden debug port and change the boot settings, which can start the device with an unrestricted command line. This means anyone with physical access could control the plug fully, potentially exposing data or disrupting service. To protect against this, keep the devices locked away, do not tamper with them, and apply any firmware updates that remove the debug interface.
What to do
- Update tp-link systems inc. kasa ec70 v4 to version 2.4.3 Build 20260902 rel.4511 or later.
- Update tp-link systems inc. kasa ec71 v4 to version 2.4.3 Build 20260902 rel.4511 or later.
Affected software
| Vendor | Product | Affected versions |
|---|---|---|
| tp-link systems inc. | kasa ec70 v4 | < 2.4.3 Build 20260902 rel.4511 |
| tp-link systems inc. | kasa ec71 v4 | < 2.4.3 Build 20260902 rel.4511 |
Original advisory text
Physical UART Access Leading to an Unauthenticated Root Shell in TP-Link Kasa EC70 and EC71
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.
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.
Internet-facing
14 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker full control
Severity
5.4
Medium
Type
CWE-1191On-Chip Debug and Test Interface With Improper Access Control
Timeline
Published1 Oct 2026
Updated3 Nov 2026
First seen1 Oct 2026
Track software like this
Free during beta