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
No CVSS.
References
Configurations
No configuration.
History
25 Oct 2026, 20:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-10-25 20:16
Updated : 2026-10-26 15:16
NVD link : CVE-2026-115635
Mitre link : CVE-2026-115635
CVE.ORG link : CVE-2026-115635
JSON object : View
Products Affected
No product.
CWE
CWE-863
Incorrect Authorization
