<?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>Mon, 05 Oct 2026 19:18:52 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-326678</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-326678</link>
      <description>EUVD-2026-326678</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-326678</guid>
    </item>
    <item>
      <title>fkie_cve-2026-48110</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-48110</link>
      <description>&lt;p&gt;Russh is a Rust SSH client &amp;amp; server library. From version 0.34.0 to before version 0.61.0, several russh client and server message handlers decoded attacker-controlled SSH strings, name-lists, and byte fields into owned allocations before applying field-specific bounds. A remote SSH peer could send oversized, high-fanout, or malformed length-prefixed fields and make the library allocate, attempt to allocate, or split data before rejecting input that should have been rejected earlier. This issue has been patched in version 0.61.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Russh is a Rust SSH client &amp;amp; server library. From version 0.34.0 to before version 0.61.0, several russh client and server message handlers decoded attacker-controlled SSH strings, name-lists, and byte fields into owned allocations before applying field-specific bounds. A remote SSH peer could send oversized, high-fanout, or malformed length-prefixed fields and make the library allocate, attempt to allocate, or split data before rejecting input that should have been rejected earlier. This issue has been patched in version 0.61.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-48110</guid>
    </item>
    <item>
      <title>GHSA-4r3c-5hpg-58qr — Russh SSH message fields were decoded through allocation-first parsers before field-specific bounds</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-4r3c-5hpg-58qr</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: russh&lt;/p&gt;
&lt;p&gt;# SSH message fields were decoded through allocation-first parsers before field-specific bounds&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Several `russh` client and server message handlers decoded attacker-controlled SSH strings, name-lists, and byte fields into owned allocations before applying field-specific bounds. A remote SSH peer could send oversized, high-fanout, or malformed length-prefixed fields and make the library allocate, attempt to allocate, or split data before rejecting input that should have been rejected earlier.&lt;/p&gt;
&lt;p&gt;### Affected Versions&lt;/p&gt;
&lt;p&gt;Oldest verified exploitable stable release: `russh 0.34.0`.&lt;/p&gt;
&lt;p&gt;- Historical stronger case: `russh &amp;gt;= 0.34.0, &amp;lt; 0.58.0`. These releases have the allocation-first KEXINIT field parsing issue and still use `CryptoVec` for inbound packet/decompression buffers. A peer can combine negotiated RFC `zlib`, rekey, compressed KEXINIT expansion, historical `CryptoVec` decompression growth, and KEXINIT name-list fanout.
- Current maintained-line case: `russh &amp;gt;= 0.58.0`, including `0.60.2`. These releases moved non-secret packet/decompression buffers off `CryptoVec`, but the allocation-first SSH field parser issue remains reachable as a `Vec`/`String`/name-list resource exhaustion issue.&lt;/p&gt;
&lt;p&gt;Prerelease coverage was not claimed for the zlib/`CryptoVec`/KEXINIT combo because the combined historical exploit shape was verified against stable `v0.34.0`-era code and reproduced the stress behavior on `v0.57.1`.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The affected parser pattern appeared across the SS…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: russh&lt;/p&gt;
&lt;p&gt;# SSH message fields were decoded through allocation-first parsers before field-specific bounds&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;Several `russh` client and server message handlers decoded attacker-controlled SSH strings, name-lists, and byte fields into owned allocations before applying field-specific bounds. A remote SSH peer could send oversized, high-fanout, or malformed length-prefixed fields and make the library allocate, attempt to allocate, or split data before rejecting input that should have been rejected earlier.&lt;/p&gt;
&lt;p&gt;### Affected Versions&lt;/p&gt;
&lt;p&gt;Oldest verified exploitable stable release: `russh 0.34.0`.&lt;/p&gt;
&lt;p&gt;- Historical stronger case: `russh &amp;gt;= 0.34.0, &amp;lt; 0.58.0`. These releases have the allocation-first KEXINIT field parsing issue and still use `CryptoVec` for inbound packet/decompression buffers. A peer can combine negotiated RFC `zlib`, rekey, compressed KEXINIT expansion, historical `CryptoVec` decompression growth, and KEXINIT name-list fanout.
- Current maintained-line case: `russh &amp;gt;= 0.58.0`, including `0.60.2`. These releases moved non-secret packet/decompression buffers off `CryptoVec`, but the allocation-first SSH field parser issue remains reachable as a `Vec`/`String`/name-list resource exhaustion issue.&lt;/p&gt;
&lt;p&gt;Prerelease coverage was not claimed for the zlib/`CryptoVec`/KEXINIT combo because the combined historical exploit shape was verified against stable `v0.34.0`-era code and reproduced the stress behavior on `v0.57.1`.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;The affected parser pattern appeared across the SS…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-4r3c-5hpg-58qr</guid>
    </item>
  </channel>
</rss>
