{"answers":{"affected":"It affects 2 products.","exploited":"There is no known exploitation of CVE-2025-15557 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-15557 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-15557 is a high-severity vulnerability in TP-Link Systems Inc. Tapo H100 v1, published on 5 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-15557 and fix it if it is affected.\n\nWhat it is: CVE-2025-15557 is a high-severity vulnerability in TP-Link Systems Inc. Tapo H100 v1, published on 5 Feb 2026. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-15557 in the wild and no public exploit code.\n\nAffected product: TP-Link Systems Inc. Tapo H100 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-2025-15557/ (Markdown: https://insights.sbomify.com/CVE-2025-15557/index.md)","id":"CVE-2025-15557","markdown":"https://insights.sbomify.com/CVE-2025-15557/index.md","name":"CVE-2025-15557","record":{"aliases":["GHSA-2x8h-ggxv-ww4j"],"analysis":{"component_type":"iot_embedded","fix_type":"patch","impacts":["data_read","data_modify"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"TP-Link Tapo smart home","requires_auth":"none","summary":"An on-path attacker can intercept and modify encrypted communications between TP-Link Tapo devices and the cloud due to improper certificate validation.","user_interaction":"required","vuln_class":"weak_cryptography"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"TPLink","cpe":[{"product":"tapo_h100_firmware","vendor":"tp-link"},{"product":"tapo_p100_firmware","vendor":"tp-link"}],"cvss":{"score":7.5,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-295","name":"Improper Certificate Validation"}],"description":"An Improper Certificate Validation vulnerability in TP-Link Tapo H100 v1 and Tapo P100 v1 allows an on-path attacker on the same network segment to intercept and modify encrypted device-cloud communications.  This may compromise the confidentiality and integrity of device-to-cloud communication, enabling manipulation of device data or operations.","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":"Improper Certificate Validation in TP-Link Tapo H100 and P100 Allows Man-in-the-Middle Attack","id":"CVE-2025-15557","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"weak_cryptography","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"Docker Desktop Docker Plugins Uncontrolled Search Path Element Local Privilege Escalation Vulnerability","id":"CVE-2025-15558"},"packages":[],"prev":{"headline":"Notepad++ Download of Code Without Integrity Check","id":"CVE-2025-15556"},"products":["Tapo H100 v1","Tapo P100 v1"],"published":"2026-02-05","related":[{"cvss_score":4.4,"headline":"Information Disclosure Vulnerability in TP-Link IoT Smart Hub","id":"CVE-2024-10523","kev_date_added":null,"published":"2024-11-04"}],"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-05","vendors":["TP-Link Systems Inc."]},"summary":"An on-path attacker can intercept and modify encrypted communications between TP-Link Tapo devices and the cloud due to improper certificate validation.","url":"https://insights.sbomify.com/CVE-2025-15557/"}