Answer in brief
CVE-2026-115635 records a Medium severity (CVSS 6.0) vulnerability in AshPostgres returns another tenant's record for a skipped upsert when return_skipped_upsert? is set. The current sources do not mark it as known exploited. The current feed maps ash-project/ash_postgres (generic), ash-project/ash-project/ash_postgres (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 6.0. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps ash-project/ash_postgres (generic), ash-project/ash-project/ash_postgres (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ash-project/ash_postgresgeneric | >=2.6.22 <2.15.2 | 2.15.2 |
| ash-project/ash-project/ash_postgresgeneric | >=af0903f1380468bbe1b61fe65acb33772b5e24a5 <8aa81220c401cae412d21078d11b3519ea25d3a9 | 8aa81220c401cae412d21078d11b3519ea25d3a9 |
Published upstream
Oct 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Oct 25, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Oct 25, 2026
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.
Quoted source text, attributed separately from HOL analysis.