# CVE-2026-105822: Server-Side Request Forgery in Tapo Cloud MQTT Proxy

Status: published. Published: 2026-11-03. Updated: 2026-11-03.

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).

## Remediation

No remediation reported in collected sources

## Affected products and versions

- TP-Link Systems Inc. / Tapo Cloud Service: ≥ 0; < N/A (affected, custom). Source: CNA: TPLink

## Severity and prioritization

- CVSS 4.0: 8.3 (high); CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:N/VA:H/SC:L/SI:N/SA:L; source: CNA: TPLink

- CISA KEV: No listing in collected sources

- EPSS: Not available

- SSVC: Not available

- Weaknesses: CWE-918

## Exploit evidence

No exploit evidence in collected sources. This is not proof of no exploitation.

## References

- https://www.tp-link.com/us/support/faq/5370/ (CNA: TPLink; vendor-advisory)

## Provenance

- CNA: TPLink: https://www.cve.org/CVERecord?id=CVE-2026-105822; retrieved 2026-11-03; source updated 2026-11-03

Revision: 632707fc9355492d72a87d25f09c4c76290269694fda4f1ff85ae174cdedfb98

Canonical: https://y2.dev/cve/CVE-2026-105822

## Agent and API access

Public CVE pages, Markdown, and JSON are free to read without an account or API key.

- Public catalog: https://y2.dev/cve/index.json. Follow nextCursor with the same search, filters, sort, and limit (1–100). A null cursor marks the end.

- WebMCP: search_cve_disclosures, get_cve_disclosure, get_cve_page_markdown, get_y2_cve_access. Available in compatible browsers.

- Cyber API: https://api.y2.dev/api/v2/cyber/cves and https://api.y2.dev/api/v2/cyber/cves/{cveId}.

- Y2 Pro or Elite: create a workspace API key with the intel:cyber scope and send Authorization: Bearer <Y2_API_KEY>. Setup: https://y2.dev/docs/api/create-key.

- x402: Pay per request without an account or API key. Omit Authorization, read the HTTP 402 PAYMENT-REQUIRED challenge, validate its current requirements, and retry with PAYMENT-SIGNATURE through an authorized payment client. These browser tools never make payments. Guide: https://y2.dev/docs/api/x402.

- OpenAPI: https://y2.dev/api/openapi.yaml. Agent access metadata: https://y2.dev/cve/agent.json.

Collected public records only. Check source status for coverage and freshness.