Is CVE-2026-105821 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-105821 being exploited in the wild.

How severe is CVE-2026-105821?

Informational severity, published 3 November 2026.

Which products and versions are affected?

TP-Link Tapo Cloud Not specified; cloud-side remediation applied.

Is there a fix for CVE-2026-105821?

No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

How is CVE-2026-105821 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-105821?

Check whether you run TP-Link Tapo Cloud at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-105821: TP-Link Tapo Cloud MQTT broken access control in proxy

CVE-2026-105821 · Severity: info · Published 2026-11-03

The Tapo Cloud MQTT broker, which handles communication for TP-Link's smart home device ecosystem, contains a flaw that allows an attacker with one Tapo device to impersonate another user's device. An attacker can obtain tokens for a target user's device and upload malicious content to their cloud storage, which the Tapo app will then display as a legitimate security event. This enables content spoofing and potential abuse of cloud services.

Vendors: TP-Link.

Quick answers

Is CVE-2026-105821 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-105821 being exploited in the wild.
How severe is CVE-2026-105821?: Informational severity, published 3 November 2026.
Which products and versions are affected?: TP-Link Tapo Cloud Not specified; cloud-side remediation applied.
Is there a fix for CVE-2026-105821?: No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-105821 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-105821?: Check whether you run TP-Link Tapo Cloud at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

The MQTT proxy fails to validate that the device ID in a proxy token request matches the authenticated device, enabling cross-device token issuance via a broken access control flaw. An authenticated attacker (who owns a Tapo device) can supply an arbitrary target device ID and receive a service token scoped to that device, then use it to upload content to the target's cloud storage or trigger further exploitation. The vulnerability requires device ownership and knowledge of the target device ID.

Affected products

TP-Link Tapo Cloud Not specified; cloud-side remediation applied

Timeline

2026-11-03: disclosed

References

https://www.tp-link.com/us/support/faq/5370/

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.