Vulnerability EEF-CVE-2026-115627

Unknown
UNKNOWN RISK
Vulnerabilities without an assigned CVSS score. Severity is not determinable from available data.
27 days ago
October 25, 2026 at 07:49 PM UTC
AshPostgres ignores attribute multitenancy on the join resource when loading many_to_many and through relationships, returning records related through other tenants' rows
0.38.0 - 0.40.0-rc1 and 0.40.0-rc2 and 0.40.0-rc3 and 0.40.0-rc4 and 0.40.0-rc5 - 0.41.0-rc.0 and 0.41.0-rc.1 and 0.41.0-rc.2 and 0.41.0-rc.3 and 0.41.0-rc.4 and 0.41.0-rc.5 and 0.41.0-rc.6 and 0.41.0-rc.7 and 0.41.0-rc.8 and 0.41.0-rc.9 and 0.41.0-rc0 - 0.42.0-rc.0 and 0.42.0-rc.1 and 0.42.0-rc.3 and 0.42.0-rc.4 and 0.42.0-rc.5 and 0.42.0-rc.6 and 0.42.0-rc.7 - 1.0.0-pre.0 and 1.0.0-pre.1 and 1.0.0-pre.2 and 1.0.0-pre.3 and 1.0.0-rc.0 and 1.0.0-rc.1 and 1.0.0-rc.2 and 1.0.0-rc.3 and 1.0.0-rc.4 and 1.0.0-rc.5 and 1.0.0-rc.6 and 1.0.0-rc.7 and 1.0.0-rc.8 and 1.0.0-rc.9 and 1.0.0 - 1.2.0-rc.0 and 1.2.0-rc.1 and 1.2.0 - 1.3.0-rc.0 and 1.3.0-rc.2 and 1.3.0-rc.3 and 1.3.0-rc.4 and 1.3.0 - 1.3.6 and 1.3.8 - 1.3.12 and 1.3.14 - 1.3.26 and 1.3.28 - 1.3.56 and 1.3.58 - 2.0.0-rc.0 and 2.0.0-rc.1 and 2.0.0-rc.2 and 2.0.0-rc.3 and 2.0.0-rc.4 and 2.0.0-rc.5 and 2.0.0-rc.6 and 2.0.0-rc.7 and 2.0.0-rc.8 and 2.0.0-rc.9 and 2.0.0-rc.10 and 2.0.0-rc.11 and 2.0.0-rc.12 and 2.0.0-rc.13 and 2.0.0-rc.14 and 2.0.0-rc.15 and 2.0.0 - 2.1.6 and 2.1.8 - 2.1.15 and 2.1.17 - 2.15.1
0.38.0 - 0.40.0-rc1 and 0.40.0-rc2 and 0.40.0-rc3 and 0.40.0-rc4 and 0.40.0-rc5 - 0.41.0-rc.0 and 0.41.0-rc.1 and 0.41.0-rc.2 and 0.41.0-rc.3 and 0.41.0-rc.4 and 0.41.0-rc.5 and 0.41.0-rc.6 and 0.41.0-rc.7 and 0.41.0-rc.8 and 0.41.0-rc.9 and 0.41.0-rc0 - 0.42.0-rc.0 and 0.42.0-rc.1 and 0.42.0-rc.3 and 0.42.0-rc.4 and 0.42.0-rc.5 and 0.42.0-rc.6 and 0.42.0-rc.7 - 1.0.0-pre.0 and 1.0.0-pre.1 and 1.0.0-pre.2 and 1.0.0-pre.3 and 1.0.0-rc.0 and 1.0.0-rc.1 and 1.0.0-rc.2 and 1.0.0-rc.3 and 1.0.0-rc.4 and 1.0.0-rc.5 and 1.0.0-rc.6 and 1.0.0-rc.7 and 1.0.0-rc.8 and 1.0.0-rc.9 and 1.0.0 - 1.2.0-rc.0 and 1.2.0-rc.1 and 1.2.0 - 1.3.0-rc.0 and 1.3.0-rc.2 and 1.3.0-rc.3 and 1.3.0-rc.4 and 1.3.0 - 1.3.6 and 1.3.8 - 1.3.12 and 1.3.14 - 1.3.26 and 1.3.28 - 1.3.56 and 1.3.58 - 2.0.0-rc.0 and 2.0.0-rc.1 and 2.0.0-rc.2 and 2.0.0-rc.3 and 2.0.0-rc.4 and 2.0.0-rc.5 and 2.0.0-rc.6 and 2.0.0-rc.7 and 2.0.0-rc.8 and 2.0.0-rc.9 and 2.0.0-rc.10 and 2.0.0-rc.11 and 2.0.0-rc.12 and 2.0.0-rc.13 and 2.0.0-rc.14 and 2.0.0-rc.15 and 2.0.0 - 2.1.6 and 2.1.8 - 2.1.15 and 2.1.17 - 2.15.1

Summary

AshPostgres ignores attribute multitenancy on the join resource when loading many_to_many and through relationships, returning records related through other tenants' rows

Details

Summary

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.

Impact

A user of one tenant loading a many_to_many or through relationship receives destination records linked only through another tenant's join rows.

Configurations

Reachable when the join resource of a many_to_many relationship, or a resource along a through path, uses attribute multitenancy and holds rows from several tenants, and the relationship is loaded with a lateral join (for example with a limit, offset or sort on the relationship).

Related Vulnerabilities

Other vulnerabilities affecting the same packages

Unknown
27 days ago
AshPostgres returns another tenant's record for a skipped upsert when return_skipped_upsert? is set
2.6.22 - 2.15.1 EEF-CVE-2026-115635
2.6.22 - 2.15.1 EEF-CVE-2026-115635
Unknown
2 months ago
rename_tenant returns :ok on a failed rename, enabling cross-tenant access in AshPostgres
0.25.0 - 0.28.1 and 0.29.1 - 0.29.6 and 0.30.1 and 0.31.1 - 0.34.5 and 0.35.1 and 0.35.3 - 0.40.0-rc1 and 0.40.0-rc2 and 0.40.0-rc3 and 0.40.0-rc4 and 0.40.0-rc5 - 0.41.0-rc.0 and 0.41.0-rc.1 and 0.41.0-rc.2 and 0.41.0-rc.3 and 0.41.0-rc.4 and 0.41.0-rc.5 and 0.41.0-rc.6 and 0.41.0-rc.7 and 0.41.0-rc.8 and 0.41.0-rc.9 and 0.41.0-rc0 - 0.42.0-rc.0 and 0.42.0-rc.1 and 0.42.0-rc.3 and 0.42.0-rc.4 and 0.42.0-rc.5 and 0.42.0-rc.6 and 0.42.0-rc.7 - 1.0.0-pre.0 and 1.0.0-pre.1 and 1.0.0-pre.2 and 1.0.0-pre.3 and 1.0.0-rc.0 and 1.0.0-rc.1 and 1.0.0-rc.2 and 1.0.0-rc.3 and 1.0.0-rc.4 and 1.0.0-rc.5 and 1.0.0-rc.6 and 1.0.0-rc.7 and 1.0.0-rc.8 and 1.0.0-rc.9 and 1.0.0 - 1.2.0-rc.0 and 1.2.0-rc.1 and 1.2.0 - 1.3.0-rc.0 and 1.3.0-rc.2 and 1.3.0-rc.3 and 1.3.0-rc.4 and 1.3.0 - 1.3.6 and 1.3.8 - 1.3.12 and 1.3.14 - 1.3.26 and 1.3.28 - 1.3.56 and 1.3.58 - 2.0.0-rc.0 and 2.0.0-rc.1 and 2.0.0-rc.2 and 2.0.0-rc.3 and 2.0.0-rc.4 and 2.0.0-rc.5 and 2.0.0-rc.6 and 2.0.0-rc.7 and 2.0.0-rc.8 and 2.0.0-rc.9 and 2.0.0-rc.10 and 2.0.0-rc.11 and 2.0.0-rc.12 and 2.0.0-rc.13 and 2.0.0-rc.14 and 2.0.0-rc.15 and 2.0.0 - 2.1.6 and 2.1.8 - 2.1.15 and 2.1.17 - 2.12.0 EEF-CVE-2026-78699
0.25.0 - 0.28.1 and 0.29.1 - 0.29.6 and 0.30.1 and 0.31.1 - 0.34.5 and 0.35.1 and 0.35.3 - 0.40.0-rc1 and 0.40.0-rc2 and 0.40.0-rc3 and 0.40.0-rc4 and 0.40.0-rc5 - 0.41.0-rc.0 and 0.41.0-rc.1 and 0.41.0-rc.2 and 0.41.0-rc.3 and 0.41.0-rc.4 and 0.41.0-rc.5 and 0.41.0-rc.6 and 0.41.0-rc.7 and 0.41.0-rc.8 and 0.41.0-rc.9 and 0.41.0-rc0 - 0.42.0-rc.0 and 0.42.0-rc.1 and 0.42.0-rc.3 and 0.42.0-rc.4 and 0.42.0-rc.5 and 0.42.0-rc.6 and 0.42.0-rc.7 - 1.0.0-pre.0 and 1.0.0-pre.1 and 1.0.0-pre.2 and 1.0.0-pre.3 and 1.0.0-rc.0 and 1.0.0-rc.1 and 1.0.0-rc.2 and 1.0.0-rc.3 and 1.0.0-rc.4 and 1.0.0-rc.5 and 1.0.0-rc.6 and 1.0.0-rc.7 and 1.0.0-rc.8 and 1.0.0-rc.9 and 1.0.0 - 1.2.0-rc.0 and 1.2.0-rc.1 and 1.2.0 - 1.3.0-rc.0 and 1.3.0-rc.2 and 1.3.0-rc.3 and 1.3.0-rc.4 and 1.3.0 - 1.3.6 and 1.3.8 - 1.3.12 and 1.3.14 - 1.3.26 and 1.3.28 - 1.3.56 and 1.3.58 - 2.0.0-rc.0 and 2.0.0-rc.1 and 2.0.0-rc.2 and 2.0.0-rc.3 and 2.0.0-rc.4 and 2.0.0-rc.5 and 2.0.0-rc.6 and 2.0.0-rc.7 and 2.0.0-rc.8 and 2.0.0-rc.9 and 2.0.0-rc.10 and 2.0.0-rc.11 and 2.0.0-rc.12 and 2.0.0-rc.13 and 2.0.0-rc.14 and 2.0.0-rc.15 and 2.0.0 - 2.1.6 and 2.1.8 - 2.1.15 and 2.1.17 - 2.12.0 EEF-CVE-2026-78699
Medium Risk
2 years ago
In AshPostgres, empty, atomic, non-bulk actions, policy bypass for side-effects vulnerability.
2.0.0 - 2.1.6 and 2.1.8 - 2.1.15 and 2.1.17 - 2.4.9 GHSA-hf59-7rwq-785m
2.0.0 - 2.1.6 and 2.1.8 - 2.1.15 and 2.1.17 - 2.4.9 GHSA-hf59-7rwq-785m
View all vulnerabilities for these packages

Impacted packages

Timeline

Published
27 days ago
October 25, 2026 at 07:49 PM UTC
Fixed (2.15.2)
27 days ago
October 25, 2026 at 06:01 PM UTC
Last Modified
2 days ago
November 20, 2026 at 06:00 AM UTC