CVE intelligence and bounded remediation

CVE-2026-34126 — Tp-Link Tapo L535E Firmware security vulnerability

High CVSS 7.5

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

Severity
High
CVSS
7.5 (3.1)
Published
2026-05-28
CISA KEV
Not currently listed
Ecosystem
operating-system
Weaknesses
CWE-319

Affected products

  • tp-link / tapo_l535e_firmware / 1.4.1
  • tp-link / tapo_p300_firmware / 1.4.0
  • tp-link / tapo_p300_firmware / 1.4.2
  • tp-link / tapo_d100c_firmware / 1.3.1

Matched remediation archetype

Cryptography, certificate, signature, and channel validation

This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.

Check exposure

  • Inventory affected algorithms, key uses, trust stores, certificate validation settings, random sources, and plaintext channels across clients and services.
  • Determine which secrets, identities, signatures, or data protections depend on the affected primitive or validation path.
  • Check debug, compatibility, fallback, and hostname or audience override settings in build and runtime configuration.

Remediate safely

  • Use a maintained platform cryptographic API with approved algorithms, modes, parameters, randomness, and full peer identity validation.
  • Remove insecure fallback and validation bypasses; separate keys by purpose and load them from managed secret storage.
  • Plan rotation or reissuance for affected keys, certificates, tokens, hashes, or ciphertext and document compatibility sequencing.

Authoritative sources

Complete CVE record and remediation plan

The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.