<?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 17:39:24 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-361836</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-361836</link>
      <description>EUVD-2026-361836</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-361836</guid>
    </item>
    <item>
      <title>fkie_cve-2026-81316</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-81316</link>
      <description>&lt;p&gt;Incorrect Authorization vulnerability in ash-project ash_sql allows a caller to receive an aggregate value computed over rows a more restrictive filter should have excluded, disclosing counts, sums, or lists across an authorization or tenancy boundary.&lt;/p&gt;
&lt;p&gt;AshSql.Aggregate.different_queries?/2 reports two aggregate queries as different only when their filter and their sort both differ. Aggregate queries rarely carry a sort, so two aggregates that share a name but carry entirely different filters compare as identical. The colliding aggregate keeps its name and is treated as already computed, and select_aggregates returns the first-registered variant&amp;#39;s value. The same name reaches the builder twice with different filters when actor or tenant context is stamped into each aggregate&amp;#39;s query, so a narrowly filtered aggregate can be served the value of a previously registered broad one.&lt;/p&gt;
&lt;p&gt;This issue affects ash_sql: from 0.1.0 before 0.7.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Incorrect Authorization vulnerability in ash-project ash_sql allows a caller to receive an aggregate value computed over rows a more restrictive filter should have excluded, disclosing counts, sums, or lists across an authorization or tenancy boundary.&lt;/p&gt;
&lt;p&gt;AshSql.Aggregate.different_queries?/2 reports two aggregate queries as different only when their filter and their sort both differ. Aggregate queries rarely carry a sort, so two aggregates that share a name but carry entirely different filters compare as identical. The colliding aggregate keeps its name and is treated as already computed, and select_aggregates returns the first-registered variant&amp;#39;s value. The same name reaches the builder twice with different filters when actor or tenant context is stamped into each aggregate&amp;#39;s query, so a narrowly filtered aggregate can be served the value of a previously registered broad one.&lt;/p&gt;
&lt;p&gt;This issue affects ash_sql: from 0.1.0 before 0.7.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-81316</guid>
    </item>
  </channel>
</rss>
