<?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 09:45:02 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-362514</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-362514</link>
      <description>EUVD-2026-362514</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-362514</guid>
    </item>
    <item>
      <title>fkie_cve-2026-82741</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-82741</link>
      <description>&lt;p&gt;Improper Validation of Specified Type of Input vulnerability in ash-project ash lets an attacker confuse the stored type tag of an Ash.Type.Union value that uses storage: :map_with_tag, bypassing that member&amp;#39;s validation and any tag-based authorization.&lt;/p&gt;
&lt;p&gt;For a union with storage: :map_with_tag, each member is identified in storage by a configured tag and tag_value. Ash.Type.Union.dump_to_native/2 (lib/ash/type/union.ex) did not force the configured tag when writing the value, so a tag carried in the submitted value was persisted verbatim. An attacker can therefore store a value whose data belongs to one member but whose tag names a different member. On read the value is re-selected by its tag and treated as the incompatible member (a type confusion), bypassing the real member&amp;#39;s constraints and any logic or policy that branches on the union tag. The fix drops any incoming tag and forces the configured tag value on dump.&lt;/p&gt;
&lt;p&gt;This issue affects ash: from 2.14.18 before 3.32.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Improper Validation of Specified Type of Input vulnerability in ash-project ash lets an attacker confuse the stored type tag of an Ash.Type.Union value that uses storage: :map_with_tag, bypassing that member&amp;#39;s validation and any tag-based authorization.&lt;/p&gt;
&lt;p&gt;For a union with storage: :map_with_tag, each member is identified in storage by a configured tag and tag_value. Ash.Type.Union.dump_to_native/2 (lib/ash/type/union.ex) did not force the configured tag when writing the value, so a tag carried in the submitted value was persisted verbatim. An attacker can therefore store a value whose data belongs to one member but whose tag names a different member. On read the value is re-selected by its tag and treated as the incompatible member (a type confusion), bypassing the real member&amp;#39;s constraints and any logic or policy that branches on the union tag. The fix drops any incoming tag and forces the configured tag value on dump.&lt;/p&gt;
&lt;p&gt;This issue affects ash: from 2.14.18 before 3.32.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-82741</guid>
    </item>
  </channel>
</rss>
