CVE-2026-115635
CVE-2026-115635 · AshPostgres returns another tenant's record for a skipped upsert when return_skipped_upsert? is set
This page contains facts from public vulnerability sources. Check the original advisory before updating.
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.
CVSS 6.0 · Medium · EPSS 0.2% · Fix available
- Published
- Updated
Affected products and versions
ash_postgres
- Versions
- ≥ 2.6.22, < 2.15.2: Affected (semver)
Update to 2.15.2
ash_postgres
- Versions
- ≥ af0903f1380468bbe1b61fe65acb33772b5e24a5, < 8aa81220c401cae412d21078d11b3519ea25d3a9: Affected (git)
No fix published
Original sources
- 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
- https://nvd.nist.gov/vuln/detail/CVE-2026-115635