{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2026-15314 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2026-15314 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-15314 is a high-severity memory corruption vulnerability in TP-Link Systems Inc. P110 v1, published on 4 Aug 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-15314 and fix it if it is affected.\n\nWhat it is: CVE-2026-15314 is a high-severity memory corruption vulnerability in TP-Link Systems Inc. P110 v1, published on 4 Aug 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-15314 in the wild and no public exploit code.\n\nAffected product: TP-Link Systems Inc. P110 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-15314/ (Markdown: https://insights.sbomify.com/CVE-2026-15314/index.md)","id":"CVE-2026-15314","markdown":"https://insights.sbomify.com/CVE-2026-15314/index.md","name":"CVE-2026-15314","record":{"aliases":["GHSA-9xv7-g9xq-gqj2"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["denial_of_service"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"Smart Wi-Fi Plug","requires_auth":"none","summary":"An authenticated attacker can cause a denial of service on the TP-Link Tapo P110 smart plug by triggering a buffer overflow via malformed HTTP requests.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TPLink","cpe":[{"product":"tapo_p110_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-120","name":"Buffer Copy without Checking Size of Input"}],"description":"Tapo P110 v1\nsmart Wi-Fi Plug contains an improper boundary validation vulnerability in the\nhandling of authenticated HTTP request bodies due to insufficient input\nvalidation before memory copy operations. This may lead to buffer overflow condition,\ncausing the web service process to crash.\n\nSuccessful exploitation\nmay cause the web service process to stop responding or restart, resulting in a\ndenial-of-service condition.","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":"Authenticated Denial-of-Service Vulnerability in TP-Link Tapo P110","id":"CVE-2026-15314","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"Unauthenticated Administrative Authentication Bypass via device_confirm Replay in TP-Link Tapo C120 and C200","id":"CVE-2026-15315"},"packages":[],"prev":{"headline":"Privilege escalation in Propovoice: All-in-One Client Management System","id":"CVE-2026-15312"},"products":["P110 v1"],"published":"2026-08-04","related":[],"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-05","vendors":["TP-Link Systems Inc."]},"summary":"An authenticated attacker can cause a denial of service on the TP-Link Tapo P110 smart plug by triggering a buffer overflow via malformed HTTP requests.","url":"https://insights.sbomify.com/CVE-2026-15314/"}