<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>VulnFeed.org: TP-Link Systems Inc. Tapo Cloud Service</title><link>https://vulnfeed.org/</link><description>Every disclosure, as it lands. Critical-only feed available.</description><language>en</language><atom:link href="https://vulnfeed.org/feed/product/tp-link-systems-inc-tapo-cloud-service.xml" rel="self" type="application/rss+xml"/><item><title>CVE-2026-105822: Server-Side Request Forgery in Tapo Cloud MQTT Proxy</title><link>https://vulnfeed.org/cve/CVE-2026-105822/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-105822/</guid><pubDate>Tue, 03 Nov 2026 20:18:06 +0000</pubDate><description>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).</description></item><item><title>CVE-2026-105821: Broken Access Control Leading to Cross-Device Token Issuance in Tapo Cloud MQTT Proxy</title><link>https://vulnfeed.org/cve/CVE-2026-105821/</link><guid isPermaLink="true">https://vulnfeed.org/cve/CVE-2026-105821/</guid><pubDate>Tue, 03 Nov 2026 20:18:05 +0000</pubDate><description>The Tapo Cloud MQTT broker contains a broken access control vulnerability in a proxy topic used by authenticated Tapo devices to request service tokens. The broker does not verify that the device ID supplied in a proxy request belongs to the authenticated device. An attacker who owns a Tapo device and knows another device&apos;s ID may obtain a device token scoped to the target device and use it to upload attacker-controlled content to the target user&apos;s Tapo Cloud storage. The content may then be presented in the Tapo app as a legitimate event. Successful exploitation may allow an attacker to upload attacker-controlled content that is presented to a target user as a legitimate Tapo event, retrieve internal service information through crafted proxy requests, or abuse Tapo Cloud outbound request capability in activity that could affect service availability.</description></item></channel></rss>
