CVE-2026-115627

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

  • Medium 6.0

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.

Key facts

Published
25 Oct 2026
Last changed
26 Oct 2026
Assigned by
EEF
EPSS
0.246% likely to be exploited in the next 30 days, higher than 15.984% of CVEs (scores for 17 Nov 2026)
SSVC (CISA)
Exploitation: none; Automatable: no; Technical impact: partial

Severity scores

Each score is shown as its source gave it. They are not averaged or merged.

  • 6.0CVSS 4.0, Mediumfrom the CNA (EEF)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

Historical context and remediation

This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.

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

No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.

Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.

Read the original CVE record.

Affected products

VendorProductVersions
ash-projectash_postgres
  • Default status: unaffected
  • 0.38.0 up to but excluding 2.15.2 (affected)
ash-projectash_postgres
  • Default status: unaffected
  • 7115bec58678f13b1ac2fb4822a0ba1aea9dbec5 up to but excluding 8c25c945c39a45299193fe70b09fc2fa2aacac7b (affected)

Timeline

  1. 25 Oct 2026 Published

Weakness

References