<?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>Wed, 07 Oct 2026 07:09:41 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-362343</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-362343</link>
      <description>EUVD-2026-362343</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-362343</guid>
    </item>
    <item>
      <title>fkie_cve-2026-82739</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-82739</link>
      <description>&lt;p&gt;Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash discloses the stored value of a confirmed field to an actor who fails its confirmation check.&lt;/p&gt;
&lt;p&gt;Ash.Resource.Validation.Confirm&amp;#39;s atomic implementation (atomic/2 in lib/ash/resource/validation/confirm.ex) built the mismatch error with its value set to the field being confirmed. When the actor supplies only the confirmation argument and not the field itself, value resolves through atomic_ref/2 to the field&amp;#39;s current stored value, so the mismatch error echoes that stored value back to the actor. Against a confirmation guarding a sensitive attribute, an actor can submit a deliberately wrong confirmation and read the real value from the returned error. The fix reports the actor-supplied confirmation in the error instead of the stored field value.&lt;/p&gt;
&lt;p&gt;This issue affects ash: from 2.17.20 before 3.32.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash discloses the stored value of a confirmed field to an actor who fails its confirmation check.&lt;/p&gt;
&lt;p&gt;Ash.Resource.Validation.Confirm&amp;#39;s atomic implementation (atomic/2 in lib/ash/resource/validation/confirm.ex) built the mismatch error with its value set to the field being confirmed. When the actor supplies only the confirmation argument and not the field itself, value resolves through atomic_ref/2 to the field&amp;#39;s current stored value, so the mismatch error echoes that stored value back to the actor. Against a confirmation guarding a sensitive attribute, an actor can submit a deliberately wrong confirmation and read the real value from the returned error. The fix reports the actor-supplied confirmation in the error instead of the stored field value.&lt;/p&gt;
&lt;p&gt;This issue affects ash: from 2.17.20 before 3.32.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-82739</guid>
    </item>
  </channel>
</rss>
