Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-34126: TP-Link has identified a vulnerability in Tapo L535E v1.0 and v3.0, Tapo P300 v1.0, and Tapo D100C v1.0, where

26
Routine
HIGH 7.5MITIGATEMITIGATEMITIGATE

CVE-2026-34126 is a high-severity flaw (CVSS 7.5) affecting tapo l535e firmware, tapo p300 firmware, tapo d100c firmware. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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, manip

Why this priority

  • High severity

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score7.5 (High)
Attack vectorAdjacent network
Attack complexityHigh
Privileges neededNone
User interactionNone
EPSS exploit chance0.1% (top 99%)
CISA exploited listNo
WeaknessCWE-319
Published2026-05-28
Last modified2026-06-17
Publisher (CNA): TPLink · Vendor: tp-link

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

tp-link tapo l535e firmware MITIGATE
Affected: 1.4.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.4.1
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
tp-link tapo p300 firmware MITIGATE
Affected: 1.4.0 · 1.4.2
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.4.0
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
tp-link tapo d100c firmware MITIGATE
Affected: 1.3.1
Fixed in: no fixed release known
Safe to downgrade to: a release before 1.3.1
Check your OS release
cat /etc/os-release; uname -r
Debian / Ubuntu
sudo apt update && sudo apt full-upgrade
RHEL / Amazon Linux / Fedora
sudo dnf upgrade --refresh
Windows
Install the latest cumulative update from Windows Update
If no patch exists yet
OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-34126?

tapo l535e firmware: mitigate or apply the listed mitigation; tapo p300 firmware: mitigate or apply the listed mitigation; tapo d100c firmware: mitigate or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2026-34126 being exploited?

CVE-2026-34126 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-34126 affect?

CVE-2026-34126 affects tapo l535e firmware, tapo p300 firmware, tapo d100c firmware. Severity is 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 du

How urgent is CVE-2026-34126?

Priority 26/100. High severity

Software pages

TP-Link vulnerabilities · Bluetooth vulnerabilities

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.