Description
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.
Affected products
Version statuses are supplied by the assigning organization. Consult the original record for detailed ranges and platform conditions.
ash-project ash_postgres
Default version status: unaffected
0.38.0 to < 2.15.2affected
pkg:hex/ash_postgresash-project ash_postgres
Default version status: unaffected
7115bec58678f13b1ac2fb4822a0ba1aea9dbec5 to < 8c25c945c39a45299193fe70b09fc2fa2aacac7baffected
pkg:github/ash-project/ash_postgresReferences
- https://github.com/ash-project/ash/security/advisories/GHSA-gr2r-f49c-9gm2 ↗
- https://cna.erlef.org/cves/CVE-2026-115627.html ↗
- https://osv.dev/vulnerability/EEF-CVE-2026-115627 ↗
- https://github.com/ash-project/ash_postgres/commit/7115bec58678f13b1ac2fb4822a0ba1aea9dbec5 ↗
- https://github.com/ash-project/ash_postgres/commit/8c25c945c39a45299193fe70b09fc2fa2aacac7b ↗