dbcve.org
Tapo L535e FirmwareOperating system · Tp Link

CVE-2026-34126

HIGH · 7.5 CVSS v3.1 Published 2026-05-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
80/100
Remediation priority · High
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
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

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 · high confidence

TP-Link Tapo devices (L535E v1.0/v3.0, P300 v1.0, D100C v1.0) transmit unencrypted Bluetooth communication during the initial setup phase. An attacker within Bluetooth range can intercept or manipulate this cleartext traffic via sniffing or man-in-the-middle techniques to potentially gain unauthorized device control.

MitigationVendors must implement encryption for Bluetooth communications during device initialization; users should perform initial setup in trusted environments away from potential attackers.

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 L535e FirmwareOperating system
Affected:= 1.4.1
Tapo P300 FirmwareOperating system
Affected:= 1.4.0= 1.4.2
Tapo D100c FirmwareOperating system
Affected:= 1.3.1

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
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:H/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 your Tapo device model
    Locate the model number on the device label or in the Tapo app device information. Common models include L535E, P300, and D100C.
    Affected if The model is L535E, P300, or D100C.
  2. Check installed firmware version
    Open the Tapo app, select the device, go to Settings > Device Info, and note the firmware version displayed. Alternatively, check the device label or packaging for the firmware version.
    Affected if Firmware version is 1.4.1 on L535E, 1.4.0 or 1.4.2 on P300, or 1.3.1 on D100C.
  3. Determine if device is in or recently completed initial setup
    Check if the device is currently going through first-time setup wizard, or if the device was recently reset to factory defaults and set up again. In the Tapo app, a device in initial setup typically shows setup prompts or onboarding screens.
    Affected if The device is currently in initial setup phase, or was set up for the first time within Bluetooth range of potential attackers.
  4. Assess Bluetooth exposure during setup
    Verify whether initial device setup was performed in a location where unknown devices could be within Bluetooth range (typically 10-100 meters). Consider if setup occurred in crowded or public areas.
    Affected if Initial setup was performed in an area with uncontrolled Bluetooth proximity.

You are affected if you own an L535E, P300, or D100C with the specific firmware versions listed AND performed or will perform initial setup in an area where attackers could be within Bluetooth range.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Vendors must implement encryption for Bluetooth communications during device initialization; users should perform initial setup in trusted environments away from potential attackers.

Fix this in Tapo L535e Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation32.0 h
  • Testing12.0 h
  • Review / QA8.0 h
58.0 hours of engineering $10,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34126 — 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-2026-34126 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