Description
Incorrect Authorization vulnerability in ash-project ash_postgres allows a user to read another tenant's record through a skipped upsert. When Ash.bulk_create/4 or a single create runs as an upsert with return_skipped_upsert?: true and the upsert is skipped (for example because its upsert_condition does not hold), AshPostgres.DataLayer reads the existing row back by the upsert identity in do_bulk_create/3 and upsert/4. That lookup did not apply the resource's attribute multitenancy, so on a resource using strategy :attribute it could match and return the row of another tenant with the same identity values, exposing its fields to the caller. This issue affects ash_postgres: from 2.6.22 before 2.15.2.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
ash-project ash_postgres
Default version status: unaffected
2.6.22 to < 2.15.2affected
pkg:hex/ash_postgresash-project ash_postgres
Default version status: unaffected
af0903f1380468bbe1b61fe65acb33772b5e24a5 to < 8aa81220c401cae412d21078d11b3519ea25d3a9affected
pkg:github/ash-project/ash_postgresReferences
- https://github.com/ash-project/ash/security/advisories/GHSA-36hg-wwp2-fg8w ↗
- https://cna.erlef.org/cves/CVE-2026-115635.html ↗
- https://osv.dev/vulnerability/EEF-CVE-2026-115635 ↗
- https://github.com/ash-project/ash_postgres/commit/af0903f1380468bbe1b61fe65acb33772b5e24a5 ↗
- https://github.com/ash-project/ash_postgres/commit/8aa81220c401cae412d21078d11b3519ea25d3a9 ↗