<?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>Fri, 16 Oct 2026 21:25:08 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-107617</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-107617</link>
      <description>&lt;p&gt;An attacker can use a hard-coded credential to log in to EseeCloud devices.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An attacker can use a hard-coded credential to log in to EseeCloud devices.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/fkie_cve-2026-107617</guid>
    </item>
    <item>
      <title>GHSA-75pm-gcg3-4jf4</title>
      <link>https://db.gcve.eu/vuln/ghsa-75pm-gcg3-4jf4</link>
      <description>&lt;p&gt;An attacker can use a hard-coded credential to log in to EseeCloud devices.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An attacker can use a hard-coded credential to log in to EseeCloud devices.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/ghsa-75pm-gcg3-4jf4</guid>
    </item>
    <item>
      <title>ICSA-26-288-02 — Guangzhou Juan IoT Technology EseeCloud</title>
      <link>https://db.gcve.eu/vuln/icsa-26-288-02</link>
      <description>&lt;p&gt;An attacker can use a hard-coded credential to log in to EseeCloud devices. An attacker can cause the server to unbind the target device from its current owner and rebind it to the requesting account, regardless of whether the device is currently bound to a different account, allowing an attacker to obtain the device&amp;#39;s full serial ID. The endpoint exposes an observable response discrepancy when processing ID values. A request submitted with a nonexistent ID returns a distinct error response code from one submitted with a valid, registered ID, allowing an attacker holding a valid access token - but without further authentication or authorization - to distinguish valid ID values from the full 10-digit numeric search space. Combined with the absence of meaningful rate limiting on this endpoint, this discrepancy constitutes an enumeration oracle, enabling an attacker to discover registered devices at scale.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An attacker can use a hard-coded credential to log in to EseeCloud devices. An attacker can cause the server to unbind the target device from its current owner and rebind it to the requesting account, regardless of whether the device is currently bound to a different account, allowing an attacker to obtain the device&amp;#39;s full serial ID. The endpoint exposes an observable response discrepancy when processing ID values. A request submitted with a nonexistent ID returns a distinct error response code from one submitted with a valid, registered ID, allowing an attacker holding a valid access token - but without further authentication or authorization - to distinguish valid ID values from the full 10-digit numeric search space. Combined with the absence of meaningful rate limiting on this endpoint, this discrepancy constitutes an enumeration oracle, enabling an attacker to discover registered devices at scale.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/icsa-26-288-02</guid>
    </item>
  </channel>
</rss>
