<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 07 Nov 2026 06:59:46 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-105821 — Broken Access Control Leading to Cross-Device Token Issuance in Tapo Cloud MQTT Proxy</title>
      <link>https://db.gcve.eu/vuln/cve-2026-105821</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; TP-Link Systems Inc. Tapo Cloud Service&lt;/p&gt;
&lt;p&gt;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&amp;#39;s ID may obtain a device token scoped to the target device and use it to
upload attacker-controlled content to the target user&amp;#39;s Tapo Cloud storage. The
content may then be presented in the Tapo app as a legitimate event.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; TP-Link Systems Inc. Tapo Cloud Service&lt;/p&gt;
&lt;p&gt;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&amp;#39;s ID may obtain a device token scoped to the target device and use it to
upload attacker-controlled content to the target user&amp;#39;s Tapo Cloud storage. The
content may then be presented in the Tapo app as a legitimate event.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-105821</guid>
    </item>
  </channel>
</rss>
