{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-0653 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-0653 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-0653 is a high-severity missing authorization 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-0653 and fix it if it is affected.\n\nWhat it is: CVE-2026-0653 is a high-severity missing authorization 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-0653 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-0653/ (Markdown: https://insights.sbomify.com/CVE-2026-0653/index.md)","id":"CVE-2026-0653","markdown":"https://insights.sbomify.com/CVE-2026-0653/index.md","name":"CVE-2026-0653","record":{"aliases":["GHSA-ghg5-7pjg-pp65"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"TP-Link Tapo camera","requires_auth":"low_privilege","summary":"Guest users can bypass access controls to modify protected device settings on TP-Link Tapo cameras and doorbells.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TPLink","cpe":[{"product":"tapo_c260_firmware","vendor":"tp-link"}],"cvss":{"score":7.2,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"On TP-Link Tapo C260 v1 and D235 v1, a guest‑level authenticated user can bypass intended access restrictions by sending crafted requests to a synchronization endpoint. This allows modification of protected device settings despite limited privileges. An attacker may change sensitive configuration parameters without authorization, resulting in unauthorized device state manipulation but not full code execution.","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":"Insecure Access Control on TP-Link Tapo D235 and C260","id":"CVE-2026-0653","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":0,"n_references":4,"next":{"headline":"Command injection on TP-Link Deco BE25","id":"CVE-2026-0654"},"packages":[],"prev":{"headline":"Remote Code Execution on TP-Link Tapo C260 by Guest User","id":"CVE-2026-0652"},"products":["Tapo C260 v1","Tapo D235 v1"],"published":"2026-02-10","related":[{"cvss_score":8.7,"headline":"Remote Code Execution on TP-Link Tapo C260 by Guest User","id":"CVE-2026-0652","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":"partial"},"state":"PUBLISHED","updated":"2026-08-04","vendors":["TP-Link Systems Inc."]},"summary":"Guest users can bypass access controls to modify protected device settings on TP-Link Tapo cameras and doorbells.","url":"https://insights.sbomify.com/CVE-2026-0653/"}