<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-06T18:21:07.208784+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-246390</id>
    <title>EUVD-2026-246390</title>
    <updated>2026-10-06T18:21:07.273571+00:00</updated>
    <content>EUVD-2026-246390</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-246390"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2025-53359</id>
    <title>fkie_cve-2025-53359</title>
    <updated>2026-10-06T18:21:07.273617+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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 "legacy" 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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2025-53359"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-3w94-vq2x-v5wr</id>
    <title>GHSA-3w94-vq2x-v5wr — ethereum does not check transaction malleability for EIP-2930, EIP-1559 and EIP-7702 transactions</title>
    <updated>2026-10-06T18:21:07.273657+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> crates.io: ethereum</p>
<p>### Impact</p>
<p>Prior to `ethereum` crate v0.18.0, signature malleability (according to EIP-2) was only checked for "legacy" transactions, but not for EIP-2930, EIP-1559 and EIP-7702 transactions.</p>
<p>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's a low/informational severity advisory.</p>
<p>### Patches</p>
<p>The issue is fixed in `ethereum` v0.18.0</p>
<p>### Workarounds</p>
<p>You can also manually check transaction malleability outside of the crate. But it's recommended to simply upgrade the version.</p>
<p>### References</p>
<p>See PR: https://github.com/rust-ethereum/ethereum/pull/67</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-3w94-vq2x-v5wr"/>
  </entry>
</feed>
