Quick answers
- Is CVE-2026-105822 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-105822 being exploited in the wild.
- How severe is CVE-2026-105822?
- Informational severity, published 3 November 2026.
- Which products and versions are affected?
- TP-Link Tapo Cloud.
- Is there a fix for CVE-2026-105822?
- Yes: fixed in Tapo Cloud backend infrastructure (cloud-side remediation; no user updates required). Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-105822 attacked?
- It is attacked over the network, in a hosted service.
- Am I affected by CVE-2026-105822?
- Check whether you run TP-Link Tapo Cloud. 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.
How to fix
- Fixed in: Tapo Cloud backend infrastructure (cloud-side remediation; no user updates required)
Technical details
The Tapo Cloud MQTT proxy fails to properly validate user-controlled host parameters before processing network requests, enabling server-side request forgery attacks. An unauthenticated network attacker can exploit this to redirect the proxy's outbound requests to arbitrary hosts, accessing internal resources or leveraging the cloud infrastructure for attacks. TP-Link remediated this on the cloud backend; no user action is required.
Affected products
- TP-Link Tapo Cloud
Timeline
- 2026-11-03: disclosed