<?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>Sun, 04 Oct 2026 22:15:16 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-252799</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-252799</link>
      <description>EUVD-2026-252799</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-252799</guid>
    </item>
    <item>
      <title>fkie_cve-2025-58749</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2025-58749</link>
      <description>&lt;p&gt;WebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime. In WAMR versions prior to 2.4.2, when running in LLVM-JIT mode, the runtime cannot exit normally when executing WebAssembly programs containing a memory.fill instruction where the first operand (memory address pointer) is greater than or equal to 2147483648 bytes (2GiB). This causes the runtime to hang in release builds or crash in debug builds due to accessing an invalid pointer. The issue does not occur in FAST-JIT mode or other runtime tools. This has been fixed in version 2.4.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;WebAssembly Micro Runtime (WAMR) is a lightweight standalone WebAssembly (Wasm) runtime. In WAMR versions prior to 2.4.2, when running in LLVM-JIT mode, the runtime cannot exit normally when executing WebAssembly programs containing a memory.fill instruction where the first operand (memory address pointer) is greater than or equal to 2147483648 bytes (2GiB). This causes the runtime to hang in release builds or crash in debug builds due to accessing an invalid pointer. The issue does not occur in FAST-JIT mode or other runtime tools. This has been fixed in version 2.4.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2025-58749</guid>
    </item>
    <item>
      <title>msrc_CVE-2025-58749 — WAMR runtime hangs or crashes with large memory.fill addresses in LLVM-JIT mode</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2025-58749</link>
      <description>msrc_CVE-2025-58749</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2025-58749</guid>
    </item>
  </channel>
</rss>
