cve.bz

CVE-2026-105822

8.3 highEPSS 0.2%

High (8.3). EPSS 0.2% estimated probability of exploitation activity in the next 30 days.

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

Severity

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
EPSS
0.2% estimated probability of exploitation activity in the next 30 days; 9th percentile. Scored 2026-11-04. A forecast for this CVE across the internet, not for your own systems.
CWE
CWE-918 Server-Side Request Forgery (SSRF)
OWASP Top 10
A01:2025 Broken Access Control
Published
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-105822 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-105822?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-105822?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-105822 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Versions

From the CNA's record in the CVE List.

ProductAffected
TP-Link Systems Inc. Tapo Cloud Servicebefore N/A

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON