Answer in brief
CVE-2026-115627 records a Medium severity (CVSS 6.0) vulnerability in AshPostgres ignores attribute multitenancy on the join resource when loading many_to_many and through relationships, returning records related through other tenants' rows. 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 | >=0.38.0 <2.15.2 | 2.15.2 |
| ash-project/ash-project/ash_postgresgeneric | >=7115bec58678f13b1ac2fb4822a0ba1aea9dbec5 <8c25c945c39a45299193fe70b09fc2fa2aacac7b | 8c25c945c39a45299193fe70b09fc2fa2aacac7b |
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 load destination records linked to a source record only through another tenant's join rows. When a many_to_many relationship, or a through relationship, is loaded with a lateral join (for example with a per-record limit or sort), AshPostgres.DataLayer builds the query for the join resource, and for each resource along a through path, in lateral_join_query/3 and through_step_queries/4 without running that resource's read action, which is where attribute multitenancy is applied. When those resources use strategy :attribute multitenancy, rows belonging to other tenants were joined, so the load returned destination records that the caller's tenant is not related to. This issue affects ash_postgres: from 0.38.0 before 2.15.2.
Quoted source text, attributed separately from HOL analysis.