<?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:23:25 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-361819</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-361819</link>
      <description>EUVD-2026-361819</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-361819</guid>
    </item>
    <item>
      <title>fkie_cve-2026-82726</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-82726</link>
      <description>&lt;p&gt;Permissive Regular Expression vulnerability in ash-project ash_phoenix lets a remote client select the tenant an Ash application uses, or degrade the request, by sending a crafted Host header.&lt;/p&gt;
&lt;p&gt;AshPhoenix.Helpers.get_subdomain/2 stripped the root domain with String.replace(host, ~r/.?#{root_host}/, &amp;#34;&amp;#34;). The root host was interpolated raw, so each . became a wildcard and any metacharacter a pattern, and the replace was global and unanchored, so a match was removed from anywhere in the string. With root_host example.com, Host: foo.exampleXcom.attacker.net returned the tenant foo.attacker.net. A metacharacter-bearing or nil root host degraded the pattern or raised on every request. The comparison was also case-sensitive, so TENANT.EXAMPLE.COM and EXAMPLE.COM slipped past the root-host allowlist. conn.host comes from the client Host header. The fix matches the root host case-insensitively and only as an exact trailing suffix.&lt;/p&gt;
&lt;p&gt;This issue affects ash_phoenix: from 2.1.26 before 2.3.25.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Permissive Regular Expression vulnerability in ash-project ash_phoenix lets a remote client select the tenant an Ash application uses, or degrade the request, by sending a crafted Host header.&lt;/p&gt;
&lt;p&gt;AshPhoenix.Helpers.get_subdomain/2 stripped the root domain with String.replace(host, ~r/.?#{root_host}/, &amp;#34;&amp;#34;). The root host was interpolated raw, so each . became a wildcard and any metacharacter a pattern, and the replace was global and unanchored, so a match was removed from anywhere in the string. With root_host example.com, Host: foo.exampleXcom.attacker.net returned the tenant foo.attacker.net. A metacharacter-bearing or nil root host degraded the pattern or raised on every request. The comparison was also case-sensitive, so TENANT.EXAMPLE.COM and EXAMPLE.COM slipped past the root-host allowlist. conn.host comes from the client Host header. The fix matches the root host case-insensitively and only as an exact trailing suffix.&lt;/p&gt;
&lt;p&gt;This issue affects ash_phoenix: from 2.1.26 before 2.3.25.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-82726</guid>
    </item>
  </channel>
</rss>
