Which versions of Tapo P110 v1 are affected by CVE-2026-15314?

Organizations deploying TP-Link Tapo P110 v1 smart plugs face operational disruption risk from network-based attacks that disable the device's web service.. A patch is available.

How to fix or mitigate CVE-2026-15314?

Within 24 hours, complete an inventory of all TP-Link Tapo P110 v1 devices in use and identify those supporting critical infrastructure or time-sensitive operations. Within 7 days, obtain the available firmware patch from the TP-Link download portal and deploy it to all identified devices, beginning with production and business-critical systems. Within 30 days, verify patch deployment across all P110 v1 devices in your environment and implement network segmentation to limit device accessibility to adjacent networks only.

Tapo P110 v1 CVE-2026-15314

Q: What is the CVSS score of CVE-2026-15314?

CVE-2026-15314 has a CVSS 4.0 base score of 7.1 (High). CVSS 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.2%.

EUVD-2026-52796 HIGH

Classic Buffer Overflow (CWE-120)

2026-08-04 TPLink

GHSA-9xv7-g9xq-gqj2

Buffer Overflow P110 V1 Tp Link Systems Inc

7.1

CVSS 4.0 · Vendor: TPLink

Severity by source

Vendor (TPLink) PRIMARY

7.1 HIGH

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

vuln.today AI

6.5 MEDIUM

Adjacent vector matches IoT local-network scope; PR:N per CVSS 4.0 input despite description ambiguity; availability-only impact with no scope change.

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

4.0 AV:A/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (TPLink).

CVSS VectorVendor: TPLink

Attack Vector

Adjacent

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

Analysis Generated

Aug 04, 2026 - 17:38 vuln.today

CVE Published

Aug 04, 2026 - 16:59 cve.org

HIGH 7.1

DescriptionCVE.org

Tapo P110 v1 smart Wi-Fi Plug contains an improper boundary validation vulnerability in the handling of authenticated HTTP request bodies due to insufficient input validation before memory copy operations. This may lead to buffer overflow condition, causing the web service process to crash.

Successful exploitation may cause the web service process to stop responding or restart, resulting in a denial-of-service condition.

AnalysisAI

Buffer overflow in the TP-Link Tapo P110 v1 smart plug's HTTP request handling allows an adjacent-network attacker to crash the web service process, resulting in a denial-of-service condition. The device's web service performs a memory copy of HTTP request body data without validating input length against the destination buffer, enabling an oversized payload to corrupt adjacent memory regions. No public exploit code or CISA KEV listing exists at time of analysis; a vendor-released firmware patch is available via the TP-Link download portal.

Technical ContextAI

The affected product is the TP-Link Tapo P110 v1 energy-monitoring smart Wi-Fi plug (CPE: cpe:2.3:a:tp-link_systems_inc.:p110_v1:*:*:*:*:*:*:*:*). The device exposes a local HTTP management interface through an embedded web server. The root cause is CWE-120 (Classic Buffer Overflow / Buffer Copy without Checking Size of Input): the code path that processes incoming HTTP request bodies performs a memory copy operation without first validating that the attacker-supplied payload length does not exceed the allocated destination buffer. This is a classic unchecked memcpy or equivalent pattern in embedded firmware. The overflow corrupts process memory, causing the web service to crash or restart. Since the CVSS 4.0 vector specifies AV:A (Adjacent), exploitation is limited to attackers on the same Layer-2 network segment as the plug - typically the home or small-office Wi-Fi network to which the device is enrolled.

RemediationAI

The primary remediation is to apply the vendor-released firmware update for the Tapo P110 v1 available at https://www.tp-link.com/us/support/download/tapo-p110/v1/#Firmware-Release-Notes and https://www.tp-link.com/en/support/download/tapo-p110/v1/#Firmware-Release-Notes; the exact patched firmware version number should be verified from the release notes on those pages as it was not independently confirmed in the available input data. Additional guidance is provided in the TP-Link advisory at https://www.tp-link.com/us/support/faq/5220/. If firmware update is not immediately possible, a compensating control is to isolate the Tapo P110 on a dedicated IoT VLAN or network segment separated from untrusted clients and guest networks, which raises the bar for exploitation by enforcing the AV:A boundary; note that this reduces convenience of shared-network access but does not eliminate the vulnerability. Disabling the device's web management interface entirely (if the Tapo app can manage the device via cloud relay without local HTTP access) would eliminate the attack surface at the cost of local management capability.