<?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://vulnerability.circl.lu</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 03:35:54 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-81886</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-81886</link>
      <description>&lt;p&gt;radare2 is a UNIX-like reverse engineering framework and command-line toolset. Prior to 6.2.0, radare2&amp;#39;s Windows 64-bit crash-dump dmp64 parser was vulnerable because the Windows dmp64 parser used an input-controlled physical-memory-run PageCount directly as the bound of a per-page allocation loop. The vulnerability is triggered by opening a small crafted full-memory Windows crash dump. The parser repeatedly allocated and appended page descriptors without validating the count against the dump size. This can cause denial of service through excessive memory consumption and processing time. This issue is fixed in version 6.2.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;radare2 is a UNIX-like reverse engineering framework and command-line toolset. Prior to 6.2.0, radare2&amp;#39;s Windows 64-bit crash-dump dmp64 parser was vulnerable because the Windows dmp64 parser used an input-controlled physical-memory-run PageCount directly as the bound of a per-page allocation loop. The vulnerability is triggered by opening a small crafted full-memory Windows crash dump. The parser repeatedly allocated and appended page descriptors without validating the count against the dump size. This can cause denial of service through excessive memory consumption and processing time. This issue is fixed in version 6.2.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-81886</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:21988-1 — Security update for radare2</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:21988-1</link>
      <description>&lt;p&gt;Security update for radare2&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for radare2&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:21988-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-81886</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-81886</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: radare2, Ubuntu:Pro:18.04:LTS: radare2, Ubuntu:Pro:20.04:LTS: radare2, Ubuntu:Pro:24.04:LTS: radare2, Ubuntu:26.04:LTS: radare2&lt;/p&gt;
&lt;p&gt;radare2 is a UNIX-like reverse engineering framework and command-line toolset. Prior to 6.2.0, radare2&amp;#39;s Windows 64-bit crash-dump dmp64 parser was vulnerable because the Windows dmp64 parser used an input-controlled physical-memory-run PageCount directly as the bound of a per-page allocation loop. The vulnerability is triggered by opening a small crafted full-memory Windows crash dump. The parser repeatedly allocated and appended page descriptors without validating the count against the dump size. This can cause denial of service through excessive memory consumption and processing time. This issue is fixed in version 6.2.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:16.04:LTS: radare2, Ubuntu:Pro:18.04:LTS: radare2, Ubuntu:Pro:20.04:LTS: radare2, Ubuntu:Pro:24.04:LTS: radare2, Ubuntu:26.04:LTS: radare2&lt;/p&gt;
&lt;p&gt;radare2 is a UNIX-like reverse engineering framework and command-line toolset. Prior to 6.2.0, radare2&amp;#39;s Windows 64-bit crash-dump dmp64 parser was vulnerable because the Windows dmp64 parser used an input-controlled physical-memory-run PageCount directly as the bound of a per-page allocation loop. The vulnerability is triggered by opening a small crafted full-memory Windows crash dump. The parser repeatedly allocated and appended page descriptors without validating the count against the dump size. This can cause denial of service through excessive memory consumption and processing time. This issue is fixed in version 6.2.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-81886</guid>
    </item>
  </channel>
</rss>
