<?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>Tue, 06 Oct 2026 23:36:56 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-309292</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-309292</link>
      <description>EUVD-2026-309292</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-309292</guid>
    </item>
    <item>
      <title>fkie_cve-2026-42278</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-42278</link>
      <description>&lt;p&gt;UltraDAG is a minimal DAG-BFT blockchain in Rust. Prior to commit fb6ef59, the UltraDAG StateEngine implementation of SmartTransferTx contains a critical logic flaw in its policy enforcement pipeline. When a transaction originates from a &amp;#34;Pocket&amp;#34; (a derived sub-address documented in the protocol as a way to organize funds), the engine fails to resolve the pocket&amp;#39;s parent account before checking the spending policy. Because pockets are &amp;#34;virtual&amp;#34; addresses that exist only as entries in the pocket_to_parent map and do not have their own SmartAccountConfig entries, the check_spending_policy method defaults to an &amp;#34;authorized/no policy&amp;#34; result. This allow any user (or attacker in possession of a parent key) to instantly drain every pocket on an account, even if the parent account has a strict 24-hour vault delay or a 1 UDAG daily limit. This issue has been patched via commit fb6ef59.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;UltraDAG is a minimal DAG-BFT blockchain in Rust. Prior to commit fb6ef59, the UltraDAG StateEngine implementation of SmartTransferTx contains a critical logic flaw in its policy enforcement pipeline. When a transaction originates from a &amp;#34;Pocket&amp;#34; (a derived sub-address documented in the protocol as a way to organize funds), the engine fails to resolve the pocket&amp;#39;s parent account before checking the spending policy. Because pockets are &amp;#34;virtual&amp;#34; addresses that exist only as entries in the pocket_to_parent map and do not have their own SmartAccountConfig entries, the check_spending_policy method defaults to an &amp;#34;authorized/no policy&amp;#34; result. This allow any user (or attacker in possession of a parent key) to instantly drain every pocket on an account, even if the parent account has a strict 24-hour vault delay or a 1 UDAG daily limit. This issue has been patched via commit fb6ef59.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-42278</guid>
    </item>
  </channel>
</rss>
