{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-102370 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102370 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102370 is a medium-severity authentication bypass vulnerability in TP-Link Systems Inc. Kasa EC70 V4, published on 1 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-102370 and fix it if it is affected.\n\nWhat it is: CVE-2026-102370 is a medium-severity authentication bypass vulnerability in TP-Link Systems Inc. Kasa EC70 V4, published on 1 Oct 2026. It can only be exploited from the same machine or local network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-102370 in the wild and no public exploit code.\n\nAffected product: TP-Link Systems Inc. Kasa EC70 V4. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-102370/ (Markdown: https://insights.sbomify.com/CVE-2026-102370/index.md)","id":"CVE-2026-102370","markdown":"https://insights.sbomify.com/CVE-2026-102370/index.md","name":"CVE-2026-102370","record":{"aliases":["GHSA-6p9x-mrgq-g8cr"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["privilege_escalation","code_execution"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Smart home camera","requires_auth":"none","summary":"Physical access allows attackers to restore debug interfaces and obtain an unauthenticated root shell on TP-Link Kasa cameras.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TPLink","cpe":[],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"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","version":"4.0"},"cwes":[{"id":"CWE-1191","name":"On-Chip Debug and Test Interface With Improper Access Control"}],"description":"Kasa EC70 v4\nand EC71 v4 do not logically disable the production debug interface at the\nfirmware or chip level and do not lock the bootloader.  Although the debug traces are physically\nsevered during manufacturing, an attacker with physical access can restore the\nconnection, interrupt the boot process, and manipulate boot parameters to enter\na non-standard initialization path that exposes an unauthenticated root shell\nduring startup.\n\nSuccessful exploitation may allow an\nattacker with physical access to obtain root-level command access during device\nstartup, resulting in loss of confidentiality, integrity, and availability for\nthe affected device. Exploitation requires device disassembly, restoration of\nthe severed debug connection, and manipulation of the boot process.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Physical UART Access Leading to an Unauthenticated Root Shell in TP-Link Kasa EC70 and EC71","id":"CVE-2026-102370","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"wsl-pro-service: Ubuntu Pro token exposed via process command-line arguments","id":"CVE-2026-102371"},"packages":[],"prev":{"headline":"Unauthenticated Remote Code Execution via MacTool Command Injection in TP-Link Tapo C120 \u0026 C200","id":"CVE-2026-102369"},"products":["Kasa EC70 V4","Kasa EC71 V4"],"published":"2026-10-01","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-10-01","vendors":["TP-Link Systems Inc."]},"summary":"Physical access allows attackers to restore debug interfaces and obtain an unauthenticated root shell on TP-Link Kasa cameras.","url":"https://insights.sbomify.com/CVE-2026-102370/"}