<?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://cve.radiocsirt.org</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 07:07:57 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-253312</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-253312</link>
      <description>EUVD-2026-253312</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-253312</guid>
    </item>
    <item>
      <title>fkie_cve-2025-57601</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-57601</link>
      <description>&lt;p&gt;AiKaan Cloud Controller uses a single hardcoded SSH private key and the username `proxyuser` for remote terminal access to all managed IoT/edge devices. When an administrator initiates &amp;#34;Open Remote Terminal&amp;#34; from the AiKaan dashboard, the controller sends this same static private key to the target device. The device then uses it to establish a reverse SSH tunnel to a remote access server, enabling browser-based SSH access for the administrator. Because the same `proxyuser` account and SSH key are reused across all customer environments: - An attacker who obtains the key (e.g., by intercepting it in transit, extracting it from the remote access server, or from a compromised admin account) can impersonate any managed device. - They can establish unauthorized reverse SSH tunnels and interact with devices without the owner&amp;#39;s consent. This is a design flaw in the authentication model: compromise of a single key compromises the trust boundary between the controller and devices.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;AiKaan Cloud Controller uses a single hardcoded SSH private key and the username `proxyuser` for remote terminal access to all managed IoT/edge devices. When an administrator initiates &amp;#34;Open Remote Terminal&amp;#34; from the AiKaan dashboard, the controller sends this same static private key to the target device. The device then uses it to establish a reverse SSH tunnel to a remote access server, enabling browser-based SSH access for the administrator. Because the same `proxyuser` account and SSH key are reused across all customer environments: - An attacker who obtains the key (e.g., by intercepting it in transit, extracting it from the remote access server, or from a compromised admin account) can impersonate any managed device. - They can establish unauthorized reverse SSH tunnels and interact with devices without the owner&amp;#39;s consent. This is a design flaw in the authentication model: compromise of a single key compromises the trust boundary between the controller and devices.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-57601</guid>
    </item>
    <item>
      <title>GHSA-fj6f-975w-5xrx</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fj6f-975w-5xrx</link>
      <description>&lt;p&gt;AiKaan Cloud Controller uses a single hardcoded SSH private key and the username `proxyuser` for remote terminal access to all managed IoT/edge devices. When an administrator initiates &amp;#34;Open Remote Terminal&amp;#34; from the AiKaan dashboard, the controller sends this same static private key to the target device. The device then uses it to establish a reverse SSH tunnel to a remote access server, enabling browser-based SSH access for the administrator. Because the same `proxyuser` account and SSH key are reused across all customer environments: - An attacker who obtains the key (e.g., by intercepting it in transit, extracting it from the remote access server, or from a compromised admin account) can impersonate any managed device. - They can establish unauthorized reverse SSH tunnels and interact with devices without the owner&amp;#39;s consent. This is a design flaw in the authentication model: compromise of a single key compromises the trust boundary between the controller and devices.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;AiKaan Cloud Controller uses a single hardcoded SSH private key and the username `proxyuser` for remote terminal access to all managed IoT/edge devices. When an administrator initiates &amp;#34;Open Remote Terminal&amp;#34; from the AiKaan dashboard, the controller sends this same static private key to the target device. The device then uses it to establish a reverse SSH tunnel to a remote access server, enabling browser-based SSH access for the administrator. Because the same `proxyuser` account and SSH key are reused across all customer environments: - An attacker who obtains the key (e.g., by intercepting it in transit, extracting it from the remote access server, or from a compromised admin account) can impersonate any managed device. - They can establish unauthorized reverse SSH tunnels and interact with devices without the owner&amp;#39;s consent. This is a design flaw in the authentication model: compromise of a single key compromises the trust boundary between the controller and devices.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fj6f-975w-5xrx</guid>
    </item>
  </channel>
</rss>
