<?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 15:04:50 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-82727 — AshPhoenix Form.Auto leaks submitted params in an unknown _union_type error message</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2026-82727</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ash-project ash_phoenix&lt;/p&gt;
&lt;p&gt;Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_phoenix writes the entire raw submitted param map into an exception message, so secrets submitted alongside a union form field leak into logs, crash reports and the dev error page.&lt;/p&gt;
&lt;p&gt;When AshPhoenix.Form.Auto builds a union sub-form and the submitted _union_type does not match a configured type, both raise sites built the message with inspect(params, pretty: true), embedding the full untrusted param map, and also inspected the internal union constraints[:types]. Because the message is constructed by the library rather than Phoenix&amp;#39;s parameter logger, config :phoenix, :filter_parameters never redacts it. An attacker controls both the trigger and the contents: submitting %{&amp;#34;_union_type&amp;#34; =&amp;gt; &amp;#34;nope&amp;#34;, &amp;#34;password&amp;#34; =&amp;gt; &amp;#34;...&amp;#34;} puts the password verbatim in the raised message. The fix reports only the offending _union_type and the valid type names, dropping the param and constraints dumps.&lt;/p&gt;
&lt;p&gt;This issue affects ash_phoenix: from 1.2.17 before 2.3.25.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ash-project ash_phoenix&lt;/p&gt;
&lt;p&gt;Generation of Error Message Containing Sensitive Information vulnerability in ash-project ash_phoenix writes the entire raw submitted param map into an exception message, so secrets submitted alongside a union form field leak into logs, crash reports and the dev error page.&lt;/p&gt;
&lt;p&gt;When AshPhoenix.Form.Auto builds a union sub-form and the submitted _union_type does not match a configured type, both raise sites built the message with inspect(params, pretty: true), embedding the full untrusted param map, and also inspected the internal union constraints[:types]. Because the message is constructed by the library rather than Phoenix&amp;#39;s parameter logger, config :phoenix, :filter_parameters never redacts it. An attacker controls both the trigger and the contents: submitting %{&amp;#34;_union_type&amp;#34; =&amp;gt; &amp;#34;nope&amp;#34;, &amp;#34;password&amp;#34; =&amp;gt; &amp;#34;...&amp;#34;} puts the password verbatim in the raised message. The fix reports only the offending _union_type and the valid type names, dropping the param and constraints dumps.&lt;/p&gt;
&lt;p&gt;This issue affects ash_phoenix: from 1.2.17 before 2.3.25.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2026-82727</guid>
    </item>
  </channel>
</rss>
