<?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>Fri, 02 Oct 2026 18:02:08 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-290410</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-290410</link>
      <description>EUVD-2026-290410</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-290410</guid>
    </item>
    <item>
      <title>fkie_cve-2026-34945</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-34945</link>
      <description>&lt;p&gt;Wasmtime is a runtime for WebAssembly. From 25.0.0 to before 36.0.7, 42.0.2, and 43.0.1, Wasmtime&amp;#39;s Winch compiler contains a bug where a 64-bit table, part of the memory64 proposal of WebAssembly, incorrectly translated the table.size instruction. This bug could lead to disclosing data on the host&amp;#39;s stack to WebAssembly guests. The host&amp;#39;s stack can possibly contain sensitive data related to other host-originating operations which is not intended to be disclosed to guests. This bug specifically arose from a mistake where the return value of table.size was statically typed as a 32-bit integer, as opposed to consulting the table&amp;#39;s index type to see how large the returned register could be. When combined with details about Wnich&amp;#39;s ABI, such as multi-value returns, this can be combined to read stack data from the host, within a guest. This vulnerability is fixed in 36.0.7, 42.0.2, and 43.0.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Wasmtime is a runtime for WebAssembly. From 25.0.0 to before 36.0.7, 42.0.2, and 43.0.1, Wasmtime&amp;#39;s Winch compiler contains a bug where a 64-bit table, part of the memory64 proposal of WebAssembly, incorrectly translated the table.size instruction. This bug could lead to disclosing data on the host&amp;#39;s stack to WebAssembly guests. The host&amp;#39;s stack can possibly contain sensitive data related to other host-originating operations which is not intended to be disclosed to guests. This bug specifically arose from a mistake where the return value of table.size was statically typed as a 32-bit integer, as opposed to consulting the table&amp;#39;s index type to see how large the returned register could be. When combined with details about Wnich&amp;#39;s ABI, such as multi-value returns, this can be combined to read stack data from the host, within a guest. This vulnerability is fixed in 36.0.7, 42.0.2, and 43.0.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-34945</guid>
    </item>
    <item>
      <title>GHSA-m9w2-8782-2946 — Wasmtime has host data leakage with 64-bit tables and Winch</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-m9w2-8782-2946</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: wasmtime&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Wasmtime&amp;#39;s Winch compiler contains a bug where a 64-bit table, part of the memory64 proposal of WebAssembly, incorrectly translated the `table.size` instruction. This bug could lead to disclosing data on the host&amp;#39;s stack to WebAssembly guests. The host&amp;#39;s stack can possibly contain sensitive data related to other host-originating operations which is not intended to be disclosed to guests.&lt;/p&gt;
&lt;p&gt;This bug specifically arose from a mistake where the return value of `table.size` was statically typed as a 32-bit integer, as opposed to consulting the table&amp;#39;s index type to see how large the returned register could be. When combined with details about Wnich&amp;#39;s ABI, such as multi-value returns, this can be combined to read stack data from the host, within a guest. This information disclosure should not be possible in WebAssembly, violates spec semantics, and is a vulnerability in Wasmtime.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Wasmtime 36.0.7, 42.0.2, and 43.0.1 have been issued to fix this bug. Users are recommended to update to these patched versions of Wasmtime.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Users of Cranelift are not affected by this issue, but users of Winch have no workarounds other than disabling the `Config::wasm_memory64` proposal.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: wasmtime&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;Wasmtime&amp;#39;s Winch compiler contains a bug where a 64-bit table, part of the memory64 proposal of WebAssembly, incorrectly translated the `table.size` instruction. This bug could lead to disclosing data on the host&amp;#39;s stack to WebAssembly guests. The host&amp;#39;s stack can possibly contain sensitive data related to other host-originating operations which is not intended to be disclosed to guests.&lt;/p&gt;
&lt;p&gt;This bug specifically arose from a mistake where the return value of `table.size` was statically typed as a 32-bit integer, as opposed to consulting the table&amp;#39;s index type to see how large the returned register could be. When combined with details about Wnich&amp;#39;s ABI, such as multi-value returns, this can be combined to read stack data from the host, within a guest. This information disclosure should not be possible in WebAssembly, violates spec semantics, and is a vulnerability in Wasmtime.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;Wasmtime 36.0.7, 42.0.2, and 43.0.1 have been issued to fix this bug. Users are recommended to update to these patched versions of Wasmtime.&lt;/p&gt;
&lt;p&gt;### Workarounds&lt;/p&gt;
&lt;p&gt;Users of Cranelift are not affected by this issue, but users of Winch have no workarounds other than disabling the `Config::wasm_memory64` proposal.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-m9w2-8782-2946</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10598-1 — libtree-sitter0_26-0.26.8-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10598-1</link>
      <description>&lt;p&gt;libtree-sitter0_26-0.26.8-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;libtree-sitter0_26-0.26.8-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10598-1</guid>
    </item>
    <item>
      <title>RUSTSEC-2026-0086 — Host data leakage with 64-bit tables and Winch</title>
      <link>https://cve.radiocsirt.org/vuln/rustsec-2026-0086</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: wasmtime&lt;/p&gt;
&lt;p&gt;This is an entry in the RustSec database for the Wasmtime security advisory
located at
https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-m9w2-8782-2946
For more information see the GitHub-hosted security advisory.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; crates.io: wasmtime&lt;/p&gt;
&lt;p&gt;This is an entry in the RustSec database for the Wasmtime security advisory
located at
https://github.com/bytecodealliance/wasmtime/security/advisories/GHSA-m9w2-8782-2946
For more information see the GitHub-hosted security advisory.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rustsec-2026-0086</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:21789-1 — Security update for tree-sitter</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:21789-1</link>
      <description>&lt;p&gt;Security update for tree-sitter&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for tree-sitter&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:21789-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-34945</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-34945</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: rust-wasmtime, Ubuntu:25.10: rust-wasmtime, Ubuntu:26.04:LTS: rust-wasmtime&lt;/p&gt;
&lt;p&gt;Wasmtime is a runtime for WebAssembly. From 25.0.0 to before 36.0.7, 42.0.2, and 43.0.1, Wasmtime&amp;#39;s Winch compiler contains a bug where a 64-bit table, part of the memory64 proposal of WebAssembly, incorrectly translated the table.size instruction. This bug could lead to disclosing data on the host&amp;#39;s stack to WebAssembly guests. The host&amp;#39;s stack can possibly contain sensitive data related to other host-originating operations which is not intended to be disclosed to guests. This bug specifically arose from a mistake where the return value of table.size was statically typed as a 32-bit integer, as opposed to consulting the table&amp;#39;s index type to see how large the returned register could be. When combined with details about Wnich&amp;#39;s ABI, such as multi-value returns, this can be combined to read stack data from the host, within a guest. This vulnerability is fixed in 36.0.7, 42.0.2, and 43.0.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:24.04:LTS: rust-wasmtime, Ubuntu:25.10: rust-wasmtime, Ubuntu:26.04:LTS: rust-wasmtime&lt;/p&gt;
&lt;p&gt;Wasmtime is a runtime for WebAssembly. From 25.0.0 to before 36.0.7, 42.0.2, and 43.0.1, Wasmtime&amp;#39;s Winch compiler contains a bug where a 64-bit table, part of the memory64 proposal of WebAssembly, incorrectly translated the table.size instruction. This bug could lead to disclosing data on the host&amp;#39;s stack to WebAssembly guests. The host&amp;#39;s stack can possibly contain sensitive data related to other host-originating operations which is not intended to be disclosed to guests. This bug specifically arose from a mistake where the return value of table.size was statically typed as a 32-bit integer, as opposed to consulting the table&amp;#39;s index type to see how large the returned register could be. When combined with details about Wnich&amp;#39;s ABI, such as multi-value returns, this can be combined to read stack data from the host, within a guest. This vulnerability is fixed in 36.0.7, 42.0.2, and 43.0.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-34945</guid>
    </item>
  </channel>
</rss>
