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.
{
"cna_assigner": "EEF",
"cwe_ids": [
"CWE-863"
],
"osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/115xxx/CVE-2026-115635.json"
}{
"extracted_events": [
{
"range": [
{
"introduced": "2.6.22"
},
{
"fixed": "2.15.2"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"introduced": "2.6.22"
},
{
"fixed": "2.15.2"
}
],
"source": "DESCRIPTION"
}
]
}
{
"extracted_events": [
{
"range": [
{
"introduced": "af0903f1380468bbe1b61fe65acb33772b5e24a5"
},
{
"fixed": "8aa81220c401cae412d21078d11b3519ea25d3a9"
}
],
"source": "AFFECTED_FIELD",
"strategy": "StandardRange"
},
{
"range": [
{
"fixed": "af0903f1380468bbe1b61fe65acb33772b5e24a5"
}
],
"source": "REFERENCES_COMMIT"
},
{
"range": [
{
"fixed": "8aa81220c401cae412d21078d11b3519ea25d3a9"
}
],
"source": "REFERENCES_COMMIT"
}
]
}