dbcve.org
Tapo H100 FirmwareOperating system · Tp Link

CVE-2025-15557

HIGH · 8.8 CVSS v3.1 Published 2026-02-05
Fix available
A fix is available. Upgrade to 1.2.6 / 1.6.1 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Tapo H100 and P100 devices fail to properly validate SSL/TLS certificates when establishing encrypted connections to TP-Link's cloud services. An on-path attacker on the same network segment can perform man-in-the-middle attacks, intercepting and modifying encrypted device-to-cloud traffic to manipulate device data or operations.

MitigationApply vendor firmware updates when available. In the meantime, isolate affected devices on dedicated network segments and avoid connecting IoT devices to untrusted or shared networks.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Tapo H100 FirmwareOperating system
Affected:< 1.6.1
Tapo P100 FirmwareOperating system
Affected:< 1.2.6

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Adjacent
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Tapo H100 or P100 devices on your network
    Locate your Tapo smart hub (H100) or smart plug (P100) devices. Check the physical device labels or use your Tapo app to list all registered devices.
    Affected if You have Tapo H100 or P100 devices in your environment.
  2. Check the firmware version of Tapo H100 devices
    Open the Tapo app, select the H100 hub, go to Device Settings > Firmware Version, or check the label on the device itself.
    Affected if The firmware version is lower than 1.6.1.
  3. Check the firmware version of Tapo P100 devices
    Open the Tapo app, select the P100 plug, go to Device Settings > Firmware Version, or check the label on the device itself.
    Affected if The firmware version is lower than 1.2.6.
  4. Confirm network connectivity to TP-Link cloud
    Check if the device is operational and connected to the internet through the Tapo app. The vulnerability only applies when the device communicates with TP-Link cloud services.
    Affected if The device is connected to the internet and communicates with TP-Link cloud (typically enabled by default for normal operation).

You are affected if you have any Tapo H100 firmware below 1.6.1 or P100 firmware below 1.2.6 that are connected to your network and TP-Link cloud services.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.2.6 / 1.6.1 or later
Fixed in 1.2.61.6.1
Interim mitigation

Apply vendor firmware updates when available. In the meantime, isolate affected devices on dedicated network segments and avoid connecting IoT devices to untrusted or shared networks.

Recommended fix High confidence

Tapo H100: Firmware 1.6.1 or later | Tapo P100: Firmware 1.2.6 or later

  1. Check the current firmware version of the Tapo device through the Tapo app or device settings
  2. Navigate to the official TP-Link support website (www.tp-link.com) and locate the firmware download page for your specific device model (Tapo H100 or Tapo P100)
  3. Download the latest firmware update - ensure version 1.6.1 or higher for Tapo H100, and version 1.2.6 or higher for Tapo P100
  4. Connect the device to a stable power source to prevent interruption during the update process
  5. Access the Tapo app, go to device settings, and select the firmware update option
  6. Follow the in-app prompts to install the downloaded firmware update
  7. After the update completes, verify the device is running the fixed firmware version
  8. After updating, re-pair the device with your Tapo account if prompted to ensure proper certificate validation is active
Caveat Firmware updates typically preserve device functionality; however, re-pairing with the Tapo app may be required after update

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Tapo H100 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15557 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15557 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data