<?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>Mon, 09 Nov 2026 15:35:20 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-96581 — An upsert on the primary key in Ash ignores attribute multitenancy, so one tenant can read, overwrite and take over ano…</title>
      <link>https://db.gcve.eu/vuln/cve-2026-96581</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ash-project ash&lt;/p&gt;
&lt;p&gt;Authorization Bypass Through User-Controlled Key vulnerability in ash-project ash allows a user of one tenant to read, overwrite and take over another tenant&amp;#39;s records via an upserting create action.&lt;/p&gt;
&lt;p&gt;Under attribute multitenancy, Ash.Actions.Create (lib/ash/actions/create/create.ex) and Ash.Actions.Create.Bulk (lib/ash/actions/create/bulk.ex) upserted on the primary key, or on an all_tenants? identity, without scoping the conflicting record to the request&amp;#39;s tenant. A caller of a create action with upsert? true that accepts the primary key, supplying a record id from another tenant, updated that record&amp;#39;s upsert fields and received all of its attributes in the result. With the default upsert fields the tenant attribute was written too, moving the record into the caller&amp;#39;s tenant. Read and update policies do not run for upserts, and tenant-scoped create policies pass because the tenant is the caller&amp;#39;s own.&lt;/p&gt;
&lt;p&gt;This issue affects ash: from 1.22.0 before 3.37.2.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; ash-project ash&lt;/p&gt;
&lt;p&gt;Authorization Bypass Through User-Controlled Key vulnerability in ash-project ash allows a user of one tenant to read, overwrite and take over another tenant&amp;#39;s records via an upserting create action.&lt;/p&gt;
&lt;p&gt;Under attribute multitenancy, Ash.Actions.Create (lib/ash/actions/create/create.ex) and Ash.Actions.Create.Bulk (lib/ash/actions/create/bulk.ex) upserted on the primary key, or on an all_tenants? identity, without scoping the conflicting record to the request&amp;#39;s tenant. A caller of a create action with upsert? true that accepts the primary key, supplying a record id from another tenant, updated that record&amp;#39;s upsert fields and received all of its attributes in the result. With the default upsert fields the tenant attribute was written too, moving the record into the caller&amp;#39;s tenant. Read and update policies do not run for upserts, and tenant-scoped create policies pass because the tenant is the caller&amp;#39;s own.&lt;/p&gt;
&lt;p&gt;This issue affects ash: from 1.22.0 before 3.37.2.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-96581</guid>
    </item>
  </channel>
</rss>
