CVE-2026-96581 Authorization Bypass Through User-Controlled Key vulnerability in ash-project ash allows a user of one tenant to read, overwrite and take ov

High 7.6 Published Updated
Exploited in the wild
Not known
Fix
Available

What is CVE-2026-96581?

CVE-2026-96581 is a high-severity vulnerability in ash-project ash, published on 26 Oct 2026.

Official 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.

Weakness: CWE-639

Which versions are affected by CVE-2026-96581?

1 open source package ship an affected version, including ash.

PackageAffectedFixed in
ash HexFrom 1.22.03.37.2

How do I fix CVE-2026-96581?

Upgrade ash to 3.37.2 or later.

Is CVE-2026-96581 being exploited?

There is no known exploitation of CVE-2026-96581 in the wild and no public exploit code.

Sources

Also known as EEF-CVE-2026-96581, GHSA-vw7c-67pf-gh96.

Is CVE-2026-96581 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free