Authorization Bypass Through User-Controlled Key vulnerability in ash-project ash allows a user of…

Why it is Yellow

• CVSS 7.6 high

References

• https://cna.erlef.org/cves/CVE-2026-96581.html
• https://github.com/ash-project/ash/commit/2333d01ddf37e5909769a513059b27e3183331c5
• https://github.com/ash-project/ash/commit/c9f0cdb31e7c084def05f3f5be69dd7bb7721754
• https://github.com/ash-project/ash/security/advisories/GHSA-vw7c-67pf-gh96
• https://osv.dev/vulnerability/EEF-CVE-2026-96581

Original description

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.