{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-12760 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-12760 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-12760 is a high-severity denial of service vulnerability in TP-Link Systems Inc. Tapo C200 v3, published on 24 Jun 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-12760 and fix it if it is affected.\n\nWhat it is: CVE-2026-12760 is a high-severity denial of service vulnerability in TP-Link Systems Inc. Tapo C200 v3, published on 24 Jun 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-12760 in the wild and no public exploit code.\n\nAffected product: TP-Link Systems Inc. Tapo C200 v3. 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-12760/ (Markdown: https://insights.sbomify.com/CVE-2026-12760/index.md)","id":"CVE-2026-12760","markdown":"https://insights.sbomify.com/CVE-2026-12760/index.md","name":"CVE-2026-12760","record":{"aliases":["GHSA-25hh-rw6j-95ch"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"IP camera","requires_auth":"none","summary":"An unauthenticated adjacent attacker can cause a temporary denial-of-service condition in TP-Link Tapo C200 cameras by sending malformed IPv4 fragmented packets.","user_interaction":"not_required","vuln_class":"denial_of_service"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TPLink","cpe":[{"product":"tapo_c200_firmware","vendor":"tp-link"}],"cvss":{"score":7.1,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-770","name":"Allocation of Resources Without Limits or Throttling"}],"description":"A denial-of-service (DoS) vulnerability has been identified in Tapo C200 v3 in the network packet handling logic due to improper handling of IPv4 fragmented packets.  An unauthenticated adjacent attacker can send crafted packets to cause excessive resource consumption, leading to instability of the device.Successful exploitation can remotely trigger a temporary denial-of-service condition, causing the camera to become unresponsive and resulting in intermittent loss of video monitoring and recording.","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":"Denial-of-Service Vulnerability via Malformed IPv4 Fragmentation Handling in TP-Link Tapo C200","id":"CVE-2026-12760","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"denial_of_service","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Auth bypass in miniOrange Social Login and Register (Discord, Google, Twitter, LinkedIn)","id":"CVE-2026-12761"},"packages":[],"prev":{"headline":"Multiple security vulnerabilities are addressed with IBM Cloud Pak for Business Automation iFixes for August 2026.","id":"CVE-2026-12759"},"products":["Tapo C200 v3"],"published":"2026-06-24","related":[{"cvss_score":9.8,"headline":"TP-LINK Tapo C200 remote code execution vulnerability","id":"CVE-2021-4045","kev_date_added":null,"published":"2022-03-07"},{"cvss_score":8.7,"headline":"Unauthenticated Access to connectAP API Endpoint on Tapo C100, C200 \u0026 C425","id":"CVE-2025-14300","kev_date_added":null,"published":"2025-12-20"},{"cvss_score":8.7,"headline":"Remote Code Execution via Stack-based Buffer Overflow in ONVIF SOAP Parser in TP-Link Tapo C200 and C520WS","id":"CVE-2025-8065","kev_date_added":null,"published":"2025-12-20"},{"cvss_score":7.1,"headline":"Denial-of-Service via Oversized Encrypted Credential Input in TP-Link Tapo C200","id":"CVE-2026-15316","kev_date_added":null,"published":"2026-08-18"},{"cvss_score":7.1,"headline":"Authenticated Stack-based Buffer Overflow in RTSP Authentication of Tapo C200","id":"CVE-2026-1871","kev_date_added":null,"published":"2026-06-02"},{"cvss_score":7.1,"headline":"Improper Content-Length Validation in HTTPS Requests on Tapo C200","id":"CVE-2025-14299","kev_date_added":null,"published":"2025-12-20"}],"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-06-24","vendors":["TP-Link Systems Inc."]},"summary":"An unauthenticated adjacent attacker can cause a temporary denial-of-service condition in TP-Link Tapo C200 cameras by sending malformed IPv4 fragmented packets.","url":"https://insights.sbomify.com/CVE-2026-12760/"}