{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-102369 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-102369 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-102369 is a high-severity command injection vulnerability in TP-Link Systems Inc. Tapo C120 v1, 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-102369 and fix it if it is affected.\n\nWhat it is: CVE-2026-102369 is a high-severity command injection vulnerability in TP-Link Systems Inc. Tapo C120 v1, 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-102369 in the wild and no public exploit code.\n\nAffected product: TP-Link Systems Inc. Tapo C120 v1. 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-102369/ (Markdown: https://insights.sbomify.com/CVE-2026-102369/index.md)","id":"CVE-2026-102369","markdown":"https://insights.sbomify.com/CVE-2026-102369/index.md","name":"CVE-2026-102369","record":{"aliases":["GHSA-xrj7-3q7x-59fm"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"adjacent_or_local","non_default_config":true,"product_category":"TP-Link Tapo camera","requires_auth":"none","summary":"An attacker on the local network can execute arbitrary commands on TP-Link Tapo cameras by replaying login data and exploiting unsanitized input in the MacTool handler.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TPLink","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-287","name":"Improper Authentication"}],"description":"Tapo C120 v1 and C200 V5\ndo not adequately protect login challenge data or sanitize\nattacker-controlled input processed by the MacTool handler. An unauthenticated\nattacker on the same local network can replay login challenge data to obtain an\nadministrative session, enable a privileged service that becomes accessible\nafter a reboot, and submit crafted input to execute arbitrary commands within\nthe device management process.\n\nSuccessful\nexploitation may allow arbitrary command execution on the camera and compromise\nthe confidentiality, integrity, and availability of the affected device.\nExploitation requires access from the same local network, replay of the login\nchallenge data, activation of the privileged service, and a device reboot.","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":"Unauthenticated Remote Code Execution via MacTool Command Injection in TP-Link Tapo C120 \u0026 C200","id":"CVE-2026-102369","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":5,"next":{"headline":"Physical UART Access Leading to an Unauthenticated Root Shell in TP-Link Kasa EC70 and EC71","id":"CVE-2026-102370"},"packages":[],"prev":{"headline":"Plaintext Storage of a Device-Specific Private Key in Tapo S505 Firmware","id":"CVE-2026-102368"},"products":["Tapo C120 v1","Tapo C200 v5"],"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":"An attacker on the local network can execute arbitrary commands on TP-Link Tapo cameras by replaying login data and exploiting unsanitized input in the MacTool handler.","url":"https://insights.sbomify.com/CVE-2026-102369/"}