<?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://db.gcve.eu</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, 30 Sep 2026 11:08:03 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-82586 — AshLua read operation aggregate bypasses the exposed-field allow-list, exposing private attributes</title>
      <link>https://db.gcve.eu/vuln/cve-2026-82586</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ash-project ash_lua&lt;/p&gt;
&lt;p&gt;Improper Protection of Alternate Path vulnerability in ash-project ash_lua allows a user-supplied Lua script to read attributes that are not on the exposed-field allow-list.&lt;/p&gt;
&lt;p&gt;AshLua exposes Ash resources to Lua scripts, gated by a manifest declaring which fields are exposed. The read action&amp;#39;s operation aggregate path in AshLua.Runtime took the field name straight from the Lua call and resolved it with only String.to_existing_atom and Ash.Query.Aggregate.new!, neither of which consults the exposed-field allow-list the normal fields path enforces. A script can therefore read the value of any attribute of any record the actor may read, including private sensitive?: true columns, via resource.read({ operation = {&amp;#34;list&amp;#34;, &amp;#34;hashed_password&amp;#34;} }); min and max give a value oracle. Anyone able to submit or influence a Lua script can reach this.&lt;/p&gt;
&lt;p&gt;This issue affects ash_lua: from 0.1.0 before 0.2.1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ash-project ash_lua&lt;/p&gt;
&lt;p&gt;Improper Protection of Alternate Path vulnerability in ash-project ash_lua allows a user-supplied Lua script to read attributes that are not on the exposed-field allow-list.&lt;/p&gt;
&lt;p&gt;AshLua exposes Ash resources to Lua scripts, gated by a manifest declaring which fields are exposed. The read action&amp;#39;s operation aggregate path in AshLua.Runtime took the field name straight from the Lua call and resolved it with only String.to_existing_atom and Ash.Query.Aggregate.new!, neither of which consults the exposed-field allow-list the normal fields path enforces. A script can therefore read the value of any attribute of any record the actor may read, including private sensitive?: true columns, via resource.read({ operation = {&amp;#34;list&amp;#34;, &amp;#34;hashed_password&amp;#34;} }); min and max give a value oracle. Anyone able to submit or influence a Lua script can reach this.&lt;/p&gt;
&lt;p&gt;This issue affects ash_lua: from 0.1.0 before 0.2.1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-82586</guid>
    </item>
  </channel>
</rss>
