{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-0652 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-0652 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-0652 is a high-severity command injection vulnerability in TP-Link Systems Inc. Tapo C260 v1, published on 10 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-0652 and fix it if it is affected.\n\nWhat it is: CVE-2026-0652 is a high-severity command injection vulnerability in TP-Link Systems Inc. Tapo C260 v1, published on 10 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-0652 in the wild and no public exploit code.\n\nAffected product: TP-Link Systems Inc. Tapo C260 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-0652/ (Markdown: https://insights.sbomify.com/CVE-2026-0652/index.md)","id":"CVE-2026-0652","markdown":"https://insights.sbomify.com/CVE-2026-0652/index.md","name":"CVE-2026-0652","record":{"aliases":["GHSA-4f5q-mmm6-fj92"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"TP-Link Tapo camera","requires_auth":"low_privilege","summary":"An authenticated attacker can execute arbitrary system commands on TP-Link Tapo C260 cameras via improper input sanitization, leading to full device compromise.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TPLink","cpe":[{"product":"tapo_c260_firmware","vendor":"tp-link"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:L/SI:L/SA:L","version":"4.0"},"cwes":[{"id":"CWE-78","name":"Improper Neutralization of Special Elements used in an OS Command"}],"description":"On TP-Link Tapo C260 v1, command injection vulnerability exists due to improper sanitization in certain POST parameters during configuration synchronization. An authenticated attacker can execute arbitrary system commands with high impact on confidentiality, integrity and availability. It may cause full device compromise.","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":"Remote Code Execution on TP-Link Tapo C260 by Guest User","id":"CVE-2026-0652","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Insecure Access Control on TP-Link Tapo D235 and C260","id":"CVE-2026-0653"},"packages":[],"prev":{"headline":"Path Traversal on TP-Link Tapo D235, C211, C520WS and C260 via Local https","id":"CVE-2026-0651"},"products":["Tapo C260 v1"],"published":"2026-02-10","related":[{"cvss_score":7.2,"headline":"Insecure Access Control on TP-Link Tapo D235 and C260","id":"CVE-2026-0653","kev_date_added":null,"published":"2026-02-10"},{"cvss_score":6.9,"headline":"Path Traversal on TP-Link Tapo D235, C211, C520WS and C260 via Local https","id":"CVE-2026-0651","kev_date_added":null,"published":"2026-02-10"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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-02-11","vendors":["TP-Link Systems Inc."]},"summary":"An authenticated attacker can execute arbitrary system commands on TP-Link Tapo C260 cameras via improper input sanitization, leading to full device compromise.","url":"https://insights.sbomify.com/CVE-2026-0652/"}