Live › vulnerability › CVE-2026-96581
Go to dashboardAsh, an Elixir framework, skips tenant scoping when an upserting create action matches an existing primary key. A user of one tenant who supplies another tenant's record id can read all of that record's attributes and move it into their own tenant.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 08:28 UTC. All times on this page are UTC.
Applications built on Ash 1.22.0 up to but not including 3.37.2 that use attribute multitenancy and have a create action with upsert? true that accepts the primary key. Exposure needs a user of one tenant to reach that create action and supply an id from another tenant. Apps without multitenancy, or without upserting create actions that accept the primary key, are not exposed.
No product ranges from the sources yet.
mix deps | grep ash (or check mix.lock) to see the installed ash versionupsert? true that accept the primary key under multitenancy (attribute strategy)ash package to 3.37.2 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
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's records via an upserting create action.
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'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'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's tenant. Read and update policies do not run for upserts, and tenant-scoped create policies pass because the tenant is the caller's own.
This issue affects ash: from 1.22.0 before 3.37.2.
This page as .md · .json · in your agent: get_signal("CVE-2026-96581")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.