CVEvulnerability
CVE-2026-115627
6.0 MEDIUM
Official page ↗
- Status
- Deferred
- Published
- 2026-10-25
- Last modified
- 2026-10-26
- Assigner
- 6b3ad84c-e1a6-4bf7-a703-f496b71e49db
- CVSS 4.0 (6b3ad84c-e1a6-4bf7-a703-f496b71e49db)
- 6.0 MEDIUM — CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
- Weaknesses
- CWE-863
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.
Related
Weakness · CWE (1)
- CWE-863 Incorrect Authorization weakness
References
- https://cna.erlef.org/cves/CVE-2026-115627.html cna.erlef.org
- https://github.com/ash-project/ash/security/advisories/GHSA-gr2r-f49c-9gm2 github.com
- https://github.com/ash-project/ash_postgres/commit/7115bec58678f13b1ac2fb4822a0ba1aea9dbec5 github.com
- https://github.com/ash-project/ash_postgres/commit/8c25c945c39a45299193fe70b09fc2fa2aacac7b github.com
- https://osv.dev/vulnerability/EEF-CVE-2026-115627 osv.dev