AshPostgres ignores attribute multitenancy on the join resource when loading many_to_many and through relationships, returning records related through other tenants' rows
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.
- Products
- ash_postgres
- Affected versions
- Not specified
- Fixed versions
- Not specified
- CVEs
- CVE-2026-115627
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 30 Oct 2026, 10:25 UTC · Revision 1
Source evidence
AshPostgres ignores attribute multitenancy on the join resource when loading many_to_many and through relationships, returning records related through other tenants' rows
core-cve · Original sourcePublished 25 Oct 2026, 19:49 UTC
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.
cve:CVE-2026-115627
ash_postgres
Fixed versions: Not specified
ash_postgres
Fixed versions: Not specified
Complete source record
{
"id": "06c952729e3dbc16a5df3433dbd427fda8f4ec4989522a48bb5c952e533e6af0",
"url": "https://www.cve.org/CVERecord?id=CVE-2026-115627",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "AshPostgres ignores attribute multitenancy on the join resource when loading many_to_many and through relationships, returning records related through other tenants' rows",
"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.",
"evidence": "cve:CVE-2026-115627",
"products": [
{
"name": {
"value": "ash_postgres",
"evidence": "/containers/cna/affected/0/product"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": []
},
{
"name": {
"value": "ash_postgres",
"evidence": "/containers/cna/affected/1/product"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "CVE-2026-115627",
"aliases": [
"CVE-2026-115627"
],
"metrics": [
{
"format": "CVSS",
"cvssV4_0": {
"Safety": "NOT_DEFINED",
"version": "4.0",
"Recovery": "NOT_DEFINED",
"baseScore": 6,
"Automatable": "NOT_DEFINED",
"attackVector": "NETWORK",
"baseSeverity": "MEDIUM",
"valueDensity": "NOT_DEFINED",
"vectorString": "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",
"providerUrgency": "NOT_DEFINED",
"userInteraction": "NONE",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"privilegesRequired": "LOW",
"subIntegrityImpact": "NONE",
"vulnIntegrityImpact": "NONE",
"subAvailabilityImpact": "NONE",
"vulnAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"affected": [
{
"cpes": [
"cpe:2.3:a:ash-project:ash_postgres:*:*:*:*:*:*:*:*"
],
"repo": "https://github.com/ash-project/ash_postgres",
"vendor": "ash-project",
"modules": [
"'Elixir.AshPostgres.DataLayer'"
],
"product": "ash_postgres",
"versions": [
{
"status": "affected",
"version": "0.38.0",
"lessThan": "2.15.2",
"versionType": "semver"
}
],
"packageURL": "pkg:hex/ash_postgres",
"packageName": "ash_postgres",
"programFiles": [
"lib/data_layer.ex"
],
"collectionURL": "https://repo.hex.pm",
"defaultStatus": "unaffected",
"programRoutines": [
{
"name": "'Elixir.AshPostgres.DataLayer':lateral_join_query/3"
},
{
"name": "'Elixir.AshPostgres.DataLayer':through_step_queries/4"
},
{
"name": "'Elixir.AshPostgres.DataLayer':run_query_with_lateral_join/4"
}
]
},
{
"cpes": [
"cpe:2.3:a:ash-project:ash_postgres:*:*:*:*:*:*:*:*"
],
"repo": "https://github.com/ash-project/ash_postgres",
"vendor": "ash-project",
"modules": [
"'Elixir.AshPostgres.DataLayer'"
],
"product": "ash_postgres",
"versions": [
{
"status": "affected",
"version": "7115bec58678f13b1ac2fb4822a0ba1aea9dbec5",
"lessThan": "8c25c945c39a45299193fe70b09fc2fa2aacac7b",
"versionType": "git"
}
],
"packageURL": "pkg:github/ash-project/ash_postgres",
"packageName": "ash-project/ash_postgres",
"programFiles": [
"lib/data_layer.ex"
],
"collectionURL": "https://github.com",
"defaultStatus": "unaffected",
"programRoutines": [
{
"name": "'Elixir.AshPostgres.DataLayer':lateral_join_query/3"
},
{
"name": "'Elixir.AshPostgres.DataLayer':through_step_queries/4"
},
{
"name": "'Elixir.AshPostgres.DataLayer':run_query_with_lateral_join/4"
}
]
}
],
"modified": "2026-10-26T14:35:21.109Z",
"provider": "cve",
"references": [
"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"
],
"provider_metadata": {
"adp": [
{
"title": "CISA ADP Vulnrichment",
"metrics": [
{
"other": {
"type": "ssvc",
"content": {
"id": "CVE-2026-115627",
"role": "CISA Coordinator",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"version": "2.0.3",
"timestamp": "2026-10-26T14:27:42.624297Z"
}
}
}
],
"providerMetadata": {
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP",
"dateUpdated": "2026-10-26T14:35:21.109Z"
}
}
],
"cna": {
"orgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"shortName": "EEF",
"dateUpdated": "2026-10-25T19:49:50.510Z"
}
}
},
"related_cves": [
{
"value": "CVE-2026-115627",
"evidence": "/cveMetadata/cveId"
}
],
"security_relevant": true,
"severity_evidence": "/containers/cna/metrics"
},
"source_id": "core-cve",
"document_id": 311570,
"published_at": "2026-10-25T19:49:50.51+00:00"
}