Read the docs

Server-side request forgery in TP-Link Tapo Cloud MQTT proxy

Priority LOW 35CWE-918Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
High
Attack requirements
None
Impact type
—
Confidentiality · integrity · availability
High · None · High
Fix status
Fixed

Attack profile from CVSS 4.0 · CNA. Fix status from CNA.

Summary

TP-Link Tapo Cloud Service contains a Cloud MQTT proxy that accepts a user-controlled host value without sufficient input validation, a server-side request forgery flaw (CWE-918). A remote attacker with no privileges can cause the Tapo Cloud service to send requests to an attacker-controlled server. Successful exploitation can expose internal information and cause potential distributed denial-of-service.

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

Description from the CNA

The Tapo Cloud MQTT proxy contains a server-side request forgery (SSRF) vulnerability because it accepts a user-controlled host value without sufficient input validation. An attacker may exploit this vulnerability to cause the Tapo Cloud service to send requests to an attacker-controlled server. Successful exploitation may cause the Tapo Cloud service to send a request to an attacker-controlled server, exposing the internal information and causing potential Distributed Denial-of-Service (DDoS).

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00197 9th percentileScored 2026-11-07
Fix Fixed Tapo Cloud Service (TP-Link Systems Inc.): N/A

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
No
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
TP-LinkTapo Cloud Servicebefore N/AN/APatch availableCNA
  • Tapo Cloud Service VendorTP-Link Affected before N/A Fixed in N/A Patch available CNA

Remediation

The sources list no fixed version for Tapo Cloud Service.

Written with Claude Haiku 5.5 from the sources below · 2026-11-03

  • Fix · CNA Tapo Cloud Service (TP-Link Systems Inc.) Fixed in N/A

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Advisory ·

    TP-Link Systems Tapo Cloud Service — tp-link.com/us/support/faq/5370

    2 records Highest priority Priority LOW 2 LOW

    Other records, highest priority first

    • TI-2026-84554 Broken access control in TP-Link Tapo Cloud MQTT proxyPriority LOW 36

Timeline

  1. 2026-11-03 Threatist record created from CVE-2026-105822
  2. 2026-11-03 Alias added: GHSA-c3pv-9mpr-ph38
  3. 2026-11-05 Priority changed: MEDIUM → LOW
  4. 2026-11-06 CISA SSVC decision points changed

References

  • TI-2023-16571 TP-Link TL-WR940N V2/V4, TL-WR841N V8/V10, and TL-WR740N V1/V2 was discovered to contain… KEVCVSS 3.1HIGH 8.8
  • TI-2023-01313 Command injection in TP-Link Archer AX21 KEVCVSS 3.1HIGH 8.8
  • TI-2020-14907 TP-Link TL-WA855RE V5 20200415-rel37464 devices allow an unauthenticated attacker (on the… KEVCVSS 3.1HIGH 8.8
  • TI-2025-08589 Authenticated RCE via Parental Control command injection KEVCVSS 4.0HIGH 8.6
  • TI-2015-02672 Directory traversal vulnerability in TP-LINK Archer C5 (1.2) with firmware before 150317… KEVCVSS 3.1HIGH 7.5
  • TI-2023-27456 Authentication bypass by spoofing in TP-Link TL-WR841N KEVCVSS 3.1MEDIUM 6.5
See all 636 →

Sources