<?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 23:41:06 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-362333</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-362333</link>
      <description>EUVD-2026-362333</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-362333</guid>
    </item>
    <item>
      <title>fkie_cve-2026-82747</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-82747</link>
      <description>&lt;p&gt;Incorrect Authorization vulnerability in ash-project ash returns records that a runtime read policy denies to any actor.&lt;/p&gt;
&lt;p&gt;When a resource has an access_type :runtime read policy (a check evaluated per record rather than compiled to a filter), Ash.Policy.Authorizer decides each record in check_result/1 (lib/ash/policy/authorizer/authorizer.ex) by discarding impossible policy scenarios and inspecting what remains. When every scenario for a record was impossible, meaning no policy can authorize it and it must be forbidden, the empty-scenario branch instead kept the record ({[record | data], authorizer, any_forbidden?}) and returned it as authorized. As a result, records the runtime read policy denies are returned to any actor. The fix forbids a record whose scenarios are all impossible.&lt;/p&gt;
&lt;p&gt;This issue affects ash: from 3.4.44 before 3.32.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Incorrect Authorization vulnerability in ash-project ash returns records that a runtime read policy denies to any actor.&lt;/p&gt;
&lt;p&gt;When a resource has an access_type :runtime read policy (a check evaluated per record rather than compiled to a filter), Ash.Policy.Authorizer decides each record in check_result/1 (lib/ash/policy/authorizer/authorizer.ex) by discarding impossible policy scenarios and inspecting what remains. When every scenario for a record was impossible, meaning no policy can authorize it and it must be forbidden, the empty-scenario branch instead kept the record ({[record | data], authorizer, any_forbidden?}) and returned it as authorized. As a result, records the runtime read policy denies are returned to any actor. The fix forbids a record whose scenarios are all impossible.&lt;/p&gt;
&lt;p&gt;This issue affects ash: from 3.4.44 before 3.32.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-82747</guid>
    </item>
  </channel>
</rss>
