<?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>Sat, 17 Oct 2026 15:21:55 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-76865</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-76865</link>
      <description>EUVD-2026-76865</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-76865</guid>
    </item>
    <item>
      <title>fkie_cve-2024-28123</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-28123</link>
      <description>&lt;p&gt;Wasmi is an efficient and lightweight WebAssembly interpreter with a focus on constrained and embedded systems. In the WASMI Interpreter, an Out-of-bounds Buffer Write will arise if the host calls or resumes a Wasm function with more parameters than the default limit (128), as it will surpass the stack value. This doesn’t affect calls from Wasm to Wasm, only from host to Wasm. This vulnerability was patched in version 0.31.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Wasmi is an efficient and lightweight WebAssembly interpreter with a focus on constrained and embedded systems. In the WASMI Interpreter, an Out-of-bounds Buffer Write will arise if the host calls or resumes a Wasm function with more parameters than the default limit (128), as it will surpass the stack value. This doesn’t affect calls from Wasm to Wasm, only from host to Wasm. This vulnerability was patched in version 0.31.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-28123</guid>
    </item>
    <item>
      <title>GHSA-75jp-vq8x-h4cq — Wasmi Out-of-bounds Write for host to Wasm calls with more than 128 Parameters</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-75jp-vq8x-h4cq</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: wasmi&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;In the WASMI Interpreter, an [Out-of-bounds Buffer Write](https://cwe.mitre.org/data/definitions/787.html) will arise arise if the host calls or resumes a Wasm function with more parameters than the default limit (128), as it will surpass the stack value. This doesn’t affect calls from Wasm to Wasm, only from host to Wasm.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;After conducting an analysis of the dependent Polkadot systems of `wasmi`: [Pallet Contracts](https://github.com/paritytech/polkadot-sdk/tree/master/substrate/frame/contracts), [Parity Signer](https://github.com/paritytech/parity-signer), and [Smoldot](https://github.com/smol-dot/smoldot), we have found that none on those systems have been affected by the issue as they are calling host to Wasm function with a small limited amount of parameters always.&lt;/p&gt;
&lt;p&gt;### Mitigations&lt;/p&gt;
&lt;p&gt;If you are using `wasmi` betwen version 0.15.0 and 0.31.0, please update it to the [0.31.1](https://github.com/paritytech/wasmi/releases/tag/v0.31.1) patch release that we just published.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Ensure no more than 128 parameters can be pass in a call from the host to a Wasm function.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;Patch PR: &amp;lt;PR&amp;gt;&lt;/p&gt;
&lt;p&gt;### Special thanks&lt;/p&gt;
&lt;p&gt;Special thanks to Stellar Development Foundation for reporting this security vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: wasmi&lt;/p&gt;
&lt;p&gt;### Summary&lt;/p&gt;
&lt;p&gt;In the WASMI Interpreter, an [Out-of-bounds Buffer Write](https://cwe.mitre.org/data/definitions/787.html) will arise arise if the host calls or resumes a Wasm function with more parameters than the default limit (128), as it will surpass the stack value. This doesn’t affect calls from Wasm to Wasm, only from host to Wasm.&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;After conducting an analysis of the dependent Polkadot systems of `wasmi`: [Pallet Contracts](https://github.com/paritytech/polkadot-sdk/tree/master/substrate/frame/contracts), [Parity Signer](https://github.com/paritytech/parity-signer), and [Smoldot](https://github.com/smol-dot/smoldot), we have found that none on those systems have been affected by the issue as they are calling host to Wasm function with a small limited amount of parameters always.&lt;/p&gt;
&lt;p&gt;### Mitigations&lt;/p&gt;
&lt;p&gt;If you are using `wasmi` betwen version 0.15.0 and 0.31.0, please update it to the [0.31.1](https://github.com/paritytech/wasmi/releases/tag/v0.31.1) patch release that we just published.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Ensure no more than 128 parameters can be pass in a call from the host to a Wasm function.&lt;/p&gt;
&lt;p&gt;### References&lt;/p&gt;
&lt;p&gt;Patch PR: &amp;lt;PR&amp;gt;&lt;/p&gt;
&lt;p&gt;### Special thanks&lt;/p&gt;
&lt;p&gt;Special thanks to Stellar Development Foundation for reporting this security vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-75jp-vq8x-h4cq</guid>
    </item>
    <item>
      <title>gsd-2024-28123</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-28123</link>
      <description>gsd-2024-28123</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-28123</guid>
    </item>
  </channel>
</rss>
