CVE-2026-115635: AshPostgres returns another tenant's record for a skipped upsert when return_skipped_upsert? is set
ash-project · ash_postgres
Fixed in 2.15.2 · Affected: ash-project ash_postgres before 2.15.2 · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 15% of scored CVEs
DescriptionCVE.org
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 products2
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- ash-project · ash_postgresfrom 2.6.22 before 2.15.2
- ash-project · ash_postgresVersions not stated
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- ash-project
- Published
- October 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-115635 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.