<?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>Tue, 06 Oct 2026 13:20:53 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-44467 — Claude Desktop: SSH Host Key Verification Bypass Allows Man-in-the-Middle Attack on Remote Sessions</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-44467</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; anthropics claude-code&lt;/p&gt;
&lt;p&gt;The Claude Desktop app gives you Claude Code with a graphical interface built for running multiple sessions side by side. From 1.2581.0 to before 1.4304.0, Claude Desktop&amp;#39;s SSH remote development feature verified only whether a hostname existed in ~/.ssh/known_hosts without comparing the server&amp;#39;s presented host key against the stored key. This allowed a network-positioned attacker to present an arbitrary SSH host key and have the connection silently accepted, enabling a man-in-the-middle attack on remote development sessions. Successful exploitation required the attacker to be in a network position to intercept SSH traffic (e.g., via ARP spoofing, rogue Wi-Fi, or DNS poisoning) and the target hostname to already have an entry in the victim&amp;#39;s known_hosts file. This vulnerability is fixed in 1.4304.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; anthropics claude-code&lt;/p&gt;
&lt;p&gt;The Claude Desktop app gives you Claude Code with a graphical interface built for running multiple sessions side by side. From 1.2581.0 to before 1.4304.0, Claude Desktop&amp;#39;s SSH remote development feature verified only whether a hostname existed in ~/.ssh/known_hosts without comparing the server&amp;#39;s presented host key against the stored key. This allowed a network-positioned attacker to present an arbitrary SSH host key and have the connection silently accepted, enabling a man-in-the-middle attack on remote development sessions. Successful exploitation required the attacker to be in a network position to intercept SSH traffic (e.g., via ARP spoofing, rogue Wi-Fi, or DNS poisoning) and the target hostname to already have an entry in the victim&amp;#39;s known_hosts file. This vulnerability is fixed in 1.4304.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-44467</guid>
    </item>
  </channel>
</rss>
