Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessPosition BLE sniffer near target
-
DeliveryWait for victim to initiate Tapo setup
-
ExploitCapture cleartext provisioning frames
-
ExecutionMITM and inject crafted setup data
-
PersistBind device to attacker credentials
-
ImpactMaintain unauthorized control of Tapo device
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A04:2025 - Cryptographic Failures
ASVS 5.0
V12 - Secure Communication Transport encryption
|
| Exploitation Conditions | Exploitation requires the attacker to be within Bluetooth radio range (typically ~10-30 meters, line-of-sight dependent) of the target device at the exact moment the victim performs initial setup or factory-reset re-provisioning - Bluetooth is used only during initialization, so the window is short and tied to user-triggered pairing. The victim must actively initiate setup via the Tapo mobile app (UI:A), and the attack requirement AT:P indicates the attacker must be present and listening during that window. No authentication is needed on the attacker side (PR:N), and the affected devices are specifically Tapo L535E v1.0/v3.0, P300 v1.0, and D100C v1.0 running pre-patch firmware; devices already updated to the fixed firmware versions, or devices long-since provisioned and not being re-paired, are not exposed to this vector. |
| Impact | The CVSS 4.0 vector (AV:A/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:L) yields 7.3 and accurately reflects the threat model: adjacent (Bluetooth-range) attack vector, low complexity, no authentication required, but passive user interaction (the victim must initiate setup) and an attack requirement (AT:P - being present during the brief initialization window) are real limiters. Confidentiality and integrity impacts are High, availability Low, and there is no scope/subsequent-system impact. No EPSS score, KEV listing, or POC was provided, so this is no public exploit identified at time of analysis. Real-world risk is moderate rather than critical: the attacker must be physically within BLE range (~10-30m) at the exact moment of setup, which constrains opportunistic exploitation but is entirely feasible for targeted attacks against high-value targets (e.g., the L535E smart lock guarding a residence) or in multi-tenant environments. The smart-lock use case is the standout concern because hijacking provisioning could yield persistent access to a physical-security device. |
| Exploit ScenarioDerived | An attacker positions a BLE sniffer (e.g., Ubertooth, nRF52840 dongle) within ~10-30 meters of a residence and waits for the victim to install a new Tapo L535E smart lock. When the victim opens the Tapo app and initiates pairing, the attacker captures the cleartext BLE provisioning frames containing Wi-Fi credentials and device-binding data, then replays or actively MITMs the setup to bind the lock to attacker-controlled cloud credentials, granting persistent unauthorized control. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – May 28, 2026
Cleartext Bluetooth transmission in TP-Link Tapo L535E, P300, and D100C devices allows adjacent attackers to intercept and manipulate initial setup data, enabling potential unauthorized device control during onboarding. The flaw stems from missing encryption on the Bluetooth pairing channel used only during initialization, and TP-Link has released patched firmware versions for all affected models. No public exploit identified at time of analysis, but the low complexity and absence of authentication make this a meaningful risk for users provisioning devices in dense urban or office environments.
RemediationAI
Vendor-released patches are available: upgrade Tapo L535E to firmware 1.4.1 Build 251016 Rel.204554 (download links at https://www.tp-link.com/us/support/download/tapo-l535e/ and the v3 variant at https://www.tp-link.com/en/support/download/tapo-l535e/v3/), Tapo P300 to JP_1.4.0 Build 260416 Rel.014037 or EU_1.4.2 Build 251219 Rel.142654 depending on region (https://www.tp-link.com/jp/support/download/tapo-p300/ and https://www.tp-link.com/en/support/download/tapo-p300/), and Tapo D100C to 1.3.1 Build 260421 Rel.031658. Because the vulnerability is exploitable only during initial setup, the most effective compensating control for unpatched units is to perform provisioning in a Bluetooth-quiet environment (e.g., away from windows, neighbors, and public spaces) and to power-cycle and re-provision any device previously set up in an untrusted location with the patched firmware preloaded; the trade-off is added friction and the need to physically verify radio isolation. Factory-resetting an already-deployed device without first updating firmware would re-expose the same cleartext window, so always apply the firmware update before any re-pairing operation.
Affected VersionsENISA
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The affected products are TP-Link Tapo smart-home devices: the L535E smart lock (v1.0 and v3.0), the P300 smart power strip (v1.0), and the D100C smart chime (v1.0) which ships bundled with multiple Tapo camera/doorbell SKUs (D130, D210, D235, D225, TD21, TDB21, TD25). During first-time provisioning, these devices use Bluetooth Low Energy as an out-of-band channel to receive Wi-Fi credentials and pairing data from the Tapo mobile app. The root cause maps to CWE-319 (Cleartext Transmission of Sensitive Information): the BLE setup channel lacks application-layer encryption, so payloads - potentially including Wi-Fi SSID/PSK and device-binding tokens - traverse the air in plaintext where any nearby BLE radio can capture them. Bluetooth is described as being used only during initialization, meaning the exposure window is limited to the provisioning event rather than steady-state operation.
Know when Tapo L535E V1 0 V3 0 gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:A/AC:L/AT:P/PR:N/UI:A/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
Lifecycle Timeline
2DescriptionCVE.org
TP-Link has identified a vulnerability in Tapo L535E v1.0 and v3.0, Tapo P300 v1.0, and Tapo D100C v1.0, where Bluetooth communication during the initial setup phase is transmitted in cleartext without encryption. Bluetooth is only used during initialization.
An attacker within the Bluetooth range could exploit this behavior using Bluetooth sniffing or man-in-the-middle techniques, which may allow eavesdropping on Bluetooth communication, manipulate transmitted setup data and potentially gain unauthorized control of the device during initialization.
An attacker within the Bluetooth range could exploit this behavior using Bluetooth sniffing or man-in-the-middle techniques, which may allow eavesdropping on Bluetooth communication, manipulate transmitted setup data and potentially gain unauthorized control of the device during initialization.
D100C is the chime delivered with your Tapo camera, and it is delivered with the following Tapo products:
D130, D210, D235, D225, TD21, TDB21 and TD25
Executive ViewAI
TP-Link Tapo smart devices (models L535E, P300, D100C) can be compromised during initial setup through Bluetooth interception, enabling attackers to gain unauthorized control of devices in your facilities. No public exploit identified at time of analysis, but with patches now available from TP-Link, immediate firmware updates are essential to secure your IoT inventory before further deployments.
Apply vendor patch. For devices awaiting patching: restrict device initialization to isolated network areas; defer setup of non-critical devices to patching windows; monitor configured devices for unauthorized state changes.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
EUVD-2026-32969
GHSA-p93f-7gcr-x8pr
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB