CVE-2026-102370
Last modified
CVE-2026-102370 is a medium-severity vulnerability rated 5.4/10 on the CVSS scale. 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.. EPSS estimates a 0.18% chance of exploitation in the next 30 days.
Description
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | 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 |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-102370?
How severe is CVE-2026-102370?
How do I fix CVE-2026-102370?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-102364mall4j through 4.0 fails to validate the sysType field in sa…5.4
- CVE-2026-102365mall4j through 4.0 fails to enforce authorization checks on …6.5
- CVE-2026-102366mall4j through 4.0 contains an unrestricted file upload vuln…4.4
- CVE-2026-102367mall4j through 4.0 contains an insufficient session expirati…5.4
- CVE-2026-102369Tapo C120 v1 and C200 V5 do not adequately protect login cha…8.7
- CVE-2026-10237A vulnerability was found in SourceCodester Water Billing Ma…4.7
- CVE-2026-102371In wsl-pro-service before 0.1.19ubuntu3, the service compone…5.7
- CVE-2026-102372GestSup versions before 3.2.61 fail to properly sanitize HTM…6.1
- CVE-2026-102373GestSup versions before 3.2.62 fail to validate ticket owner…6.5
- CVE-2026-102374GestSup versions before 3.2.62 contain a stored cross-site s…6.1
- CVE-2026-102375Subscriber Broken Access Control in Optimole <= 4.2.14 versi…6.5
- CVE-2026-102376Subscriber Cross Site Scripting (XSS) in Branda <= 3.4.32 ve…7.1
Are you affected by CVE-2026-102370?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
