<?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 20:58:10 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-246390</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-246390</link>
      <description>EUVD-2026-246390</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-246390</guid>
    </item>
    <item>
      <title>fkie_cve-2025-53359</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-53359</link>
      <description>&lt;p&gt;ethereum is a common ethereum structs for Rust. Prior to ethereum crate v0.18.0, signature malleability (according to EIP-2) was only checked for &amp;#34;legacy&amp;#34; transactions, but not for EIP-2930, EIP-1559 and EIP-7702 transactions. This is a specification deviation. The signature malleability itself is not a security issue and not as high of a risk if the ethereum crate is used on a single-implementation blockchain. This issue has been patched in version v0.18.0. A workaround for this issue involves manually checking transaction malleability outside of the crate, however upgrading is recommended.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;ethereum is a common ethereum structs for Rust. Prior to ethereum crate v0.18.0, signature malleability (according to EIP-2) was only checked for &amp;#34;legacy&amp;#34; transactions, but not for EIP-2930, EIP-1559 and EIP-7702 transactions. This is a specification deviation. The signature malleability itself is not a security issue and not as high of a risk if the ethereum crate is used on a single-implementation blockchain. This issue has been patched in version v0.18.0. A workaround for this issue involves manually checking transaction malleability outside of the crate, however upgrading is recommended.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-53359</guid>
    </item>
    <item>
      <title>GHSA-3w94-vq2x-v5wr — ethereum does not check transaction malleability for EIP-2930, EIP-1559 and EIP-7702 transactions</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3w94-vq2x-v5wr</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: ethereum&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Prior to `ethereum` crate v0.18.0, signature malleability (according to EIP-2) was only checked for &amp;#34;legacy&amp;#34; transactions, but not for EIP-2930, EIP-1559 and EIP-7702 transactions.&lt;/p&gt;
&lt;p&gt;This is a specification deviation and therefore a high severity advisory if the `ethereum` crate is used for Ethereum mainnet. Note that signature malleability itself is not a security issue, and therefore if the `ethereum` crate is used on a single-implementation blockchain, it&amp;#39;s a low/informational severity advisory.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue is fixed in `ethereum` v0.18.0&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;You can also manually check transaction malleability outside of the crate. But it&amp;#39;s recommended to simply upgrade the version.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;See PR: https://github.com/rust-ethereum/ethereum/pull/67&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: ethereum&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Prior to `ethereum` crate v0.18.0, signature malleability (according to EIP-2) was only checked for &amp;#34;legacy&amp;#34; transactions, but not for EIP-2930, EIP-1559 and EIP-7702 transactions.&lt;/p&gt;
&lt;p&gt;This is a specification deviation and therefore a high severity advisory if the `ethereum` crate is used for Ethereum mainnet. Note that signature malleability itself is not a security issue, and therefore if the `ethereum` crate is used on a single-implementation blockchain, it&amp;#39;s a low/informational severity advisory.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;The issue is fixed in `ethereum` v0.18.0&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;You can also manually check transaction malleability outside of the crate. But it&amp;#39;s recommended to simply upgrade the version.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;See PR: https://github.com/rust-ethereum/ethereum/pull/67&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-3w94-vq2x-v5wr</guid>
    </item>
  </channel>
</rss>
