CVE-2026-115627 (GCVE-0-2026-115627)
Vulnerability from cvelistv5 – Published: 2026-10-25 19:49 – Updated: 2026-10-26 14:35
VLAI
EPSS
VEX
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.
Severity
SSVC
Exploitation: none
Automatable: no
Technical Impact: partial
CISA Coordinator · CISA-ADP (v2.0.3)
Decision recorded 2026-10-26 14:27 UTC
CWE
- CWE-863 - Incorrect Authorization
Assigner
References
5 references
| URL | Tags |
|---|---|
| https://github.com/ash-project/ash/security/advis… | vendor-advisoryrelated |
| https://cna.erlef.org/cves/CVE-2026-115627.html | related |
| https://osv.dev/vulnerability/EEF-CVE-2026-115627 | related |
| https://github.com/ash-project/ash_postgres/commi… | related |
| https://github.com/ash-project/ash_postgres/commi… | patch |
Impacted products
2 products
| Vendor | Product | Version | CPE status | |
|---|---|---|---|---|
| ash-project | ash_postgres |
Affected:
0.38.0 , < 2.15.2
(semver)
cpe:2.3:a:ash-project:ash_postgres:*:*:*:*:*:*:*:* |
||
| ash-project | ash_postgres |
Affected:
7115bec58678f13b1ac2fb4822a0ba1aea9dbec5 , < 8c25c945c39a45299193fe70b09fc2fa2aacac7b
(git)
cpe:2.3:a:ash-project:ash_postgres:*:*:*:*:*:*:*:* |
{
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-115627",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-26T14:27:42.624297Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-10-26T14:35:21.109Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"collectionURL": "https://repo.hex.pm",
"cpes": [
"cpe:2.3:a:ash-project:ash_postgres:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"\u0027Elixir.AshPostgres.DataLayer\u0027"
],
"packageName": "ash_postgres",
"packageURL": "pkg:hex/ash_postgres",
"product": "ash_postgres",
"programFiles": [
"lib/data_layer.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:lateral_join_query/3"
},
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:through_step_queries/4"
},
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:run_query_with_lateral_join/4"
}
],
"repo": "https://github.com/ash-project/ash_postgres",
"vendor": "ash-project",
"versions": [
{
"lessThan": "2.15.2",
"status": "affected",
"version": "0.38.0",
"versionType": "semver"
}
]
},
{
"collectionURL": "https://github.com",
"cpes": [
"cpe:2.3:a:ash-project:ash_postgres:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"\u0027Elixir.AshPostgres.DataLayer\u0027"
],
"packageName": "ash-project/ash_postgres",
"packageURL": "pkg:github/ash-project/ash_postgres",
"product": "ash_postgres",
"programFiles": [
"lib/data_layer.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:lateral_join_query/3"
},
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:through_step_queries/4"
},
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:run_query_with_lateral_join/4"
}
],
"repo": "https://github.com/ash-project/ash_postgres",
"vendor": "ash-project",
"versions": [
{
"lessThan": "8c25c945c39a45299193fe70b09fc2fa2aacac7b",
"status": "affected",
"version": "7115bec58678f13b1ac2fb4822a0ba1aea9dbec5",
"versionType": "git"
}
]
}
],
"configurations": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eReachable when the join resource of a \u003ccode\u003emany_to_many\u003c/code\u003e relationship, or a resource along a \u003ccode\u003ethrough\u003c/code\u003e 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).\u003c/p\u003e"
},
{
"base64": false,
"type": "text/markdown",
"value": "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)."
}
],
"value": "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)."
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:ash-project:ash_postgres:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2.15.2",
"versionStartIncluding": "0.38.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "AND"
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Will Townsend"
},
{
"lang": "en",
"type": "reporter",
"value": "Will Townsend"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Zach Daniel / Ash Project"
}
],
"dateAssigned": "2026-10-25T17:27:14.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eIncorrect Authorization vulnerability in ash-project ash_postgres allows a user to load destination records linked to a source record only through another tenant\u0027s join rows.\u003c/p\u003e\n\u003cp\u003eWhen a \u003ccode\u003emany_to_many\u003c/code\u003e relationship, or a \u003ccode\u003ethrough\u003c/code\u003e relationship, is loaded with a lateral join (for example with a per-record limit or sort), \u003ccode\u003eAshPostgres.DataLayer\u003c/code\u003e builds the query for the join resource, and for each resource along a \u003ccode\u003ethrough\u003c/code\u003e path, in \u003ccode\u003elateral_join_query/3\u003c/code\u003e and \u003ccode\u003ethrough_step_queries/4\u003c/code\u003e without running that resource\u0027s read action, which is where attribute multitenancy is applied. When those resources use \u003ccode\u003estrategy :attribute\u003c/code\u003e multitenancy, rows belonging to other tenants were joined, so the load returned destination records that the caller\u0027s tenant is not related to.\u003c/p\u003e\n\u003cp\u003eThis issue affects ash_postgres: from 0.38.0 before 2.15.2.\u003c/p\u003e"
},
{
"base64": false,
"type": "text/markdown",
"value": "Incorrect Authorization vulnerability in ash-project ash_postgres allows a user to load destination records linked to a source record only through another tenant\u0027s join rows.\n\nWhen 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\u0027s 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\u0027s tenant is not related to.\n\nThis issue affects ash_postgres: from 0.38.0 before 2.15.2."
}
],
"value": "Incorrect Authorization vulnerability in ash-project ash_postgres allows a user to load destination records linked to a source record only through another tenant\u0027s join rows.\n\nWhen 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\u0027s 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\u0027s tenant is not related to.\n\nThis issue affects ash_postgres: from 0.38.0 before 2.15.2."
}
],
"impacts": [
{
"capecId": "CAPEC-1",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eA user of one tenant loading a many_to_many or through relationship receives destination records linked only through another tenant\u0027s join rows.\u003c/p\u003e"
},
{
"base64": false,
"type": "text/markdown",
"value": "A user of one tenant loading a many_to_many or through relationship receives destination records linked only through another tenant\u0027s join rows."
}
],
"value": "A user of one tenant loading a many_to_many or through relationship receives destination records linked only through another tenant\u0027s join rows."
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 6,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"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",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-863",
"description": "CWE-863 Incorrect Authorization",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-25T19:49:50.510Z",
"orgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"shortName": "EEF"
},
"references": [
{
"name": "AshPostgres ignores attribute multitenancy on the join resource when loading `many_to_many` and `through` relationships, returning records related through other tenants\u0027 rows",
"tags": [
"vendor-advisory",
"related"
],
"url": "https://github.com/ash-project/ash/security/advisories/GHSA-gr2r-f49c-9gm2"
},
{
"name": "EEF CNA record for CVE-2026-115627",
"tags": [
"related"
],
"url": "https://cna.erlef.org/cves/CVE-2026-115627.html"
},
{
"name": "OSV record EEF-CVE-2026-115627",
"tags": [
"related"
],
"url": "https://osv.dev/vulnerability/EEF-CVE-2026-115627"
},
{
"name": "Introducing commit 7115bec in ash-project/ash_postgres",
"tags": [
"related"
],
"url": "https://github.com/ash-project/ash_postgres/commit/7115bec58678f13b1ac2fb4822a0ba1aea9dbec5"
},
{
"name": "Fix commit 8c25c94 in ash-project/ash_postgres",
"tags": [
"patch"
],
"url": "https://github.com/ash-project/ash_postgres/commit/8c25c945c39a45299193fe70b09fc2fa2aacac7b"
}
],
"source": {
"discovery": "EXTERNAL"
},
"title": "AshPostgres ignores attribute multitenancy on the join resource when loading many_to_many and through relationships, returning records related through other tenants\u0027 rows"
}
},
"cveMetadata": {
"assignerOrgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"assignerShortName": "EEF",
"cveId": "CVE-2026-115627",
"datePublished": "2026-10-25T19:49:50.510Z",
"dateReserved": "2026-10-23T13:00:02.154Z",
"dateUpdated": "2026-10-26T14:35:21.109Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-115627",
"date": "2026-11-07",
"epss": "0.00246",
"percentile": "0.1594"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"collectionURL": "https://repo.hex.pm",
"cpes": [
"cpe:2.3:a:ash-project:ash_postgres:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"\u0027Elixir.AshPostgres.DataLayer\u0027"
],
"packageName": "ash_postgres",
"packageURL": "pkg:hex/ash_postgres",
"product": "ash_postgres",
"programFiles": [
"lib/data_layer.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:lateral_join_query/3"
},
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:through_step_queries/4"
},
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:run_query_with_lateral_join/4"
}
],
"repo": "https://github.com/ash-project/ash_postgres",
"vendor": "ash-project",
"versions": [
{
"lessThan": "2.15.2",
"status": "affected",
"version": "0.38.0",
"versionType": "semver"
}
]
},
{
"collectionURL": "https://github.com",
"cpes": [
"cpe:2.3:a:ash-project:ash_postgres:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"\u0027Elixir.AshPostgres.DataLayer\u0027"
],
"packageName": "ash-project/ash_postgres",
"packageURL": "pkg:github/ash-project/ash_postgres",
"product": "ash_postgres",
"programFiles": [
"lib/data_layer.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:lateral_join_query/3"
},
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:through_step_queries/4"
},
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:run_query_with_lateral_join/4"
}
],
"repo": "https://github.com/ash-project/ash_postgres",
"vendor": "ash-project",
"versions": [
{
"lessThan": "8c25c945c39a45299193fe70b09fc2fa2aacac7b",
"status": "affected",
"version": "7115bec58678f13b1ac2fb4822a0ba1aea9dbec5",
"versionType": "git"
}
]
}
],
"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Incorrect Authorization vulnerability in ash-project ash_postgres allows a user to load destination records linked to a source record only through another tenant\u0027s join rows.\n\nWhen 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\u0027s 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\u0027s tenant is not related to.\n\nThis issue affects ash_postgres: from 0.38.0 before 2.15.2."
}
],
"id": "CVE-2026-115627",
"lastModified": "2026-10-26T15:16:39.097",
"metrics": {
"cvssMetricV40": [
{
"cvssData": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"availabilityRequirement": "NOT_DEFINED",
"baseScore": 6.0,
"baseSeverity": "MEDIUM",
"confidentialityRequirement": "NOT_DEFINED",
"exploitMaturity": "NOT_DEFINED",
"integrityRequirement": "NOT_DEFINED",
"modifiedAttackComplexity": "NOT_DEFINED",
"modifiedAttackRequirements": "NOT_DEFINED",
"modifiedAttackVector": "NOT_DEFINED",
"modifiedPrivilegesRequired": "NOT_DEFINED",
"modifiedSubAvailabilityImpact": "NOT_DEFINED",
"modifiedSubConfidentialityImpact": "NOT_DEFINED",
"modifiedSubIntegrityImpact": "NOT_DEFINED",
"modifiedUserInteraction": "NOT_DEFINED",
"modifiedVulnAvailabilityImpact": "NOT_DEFINED",
"modifiedVulnConfidentialityImpact": "NOT_DEFINED",
"modifiedVulnIntegrityImpact": "NOT_DEFINED",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"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/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",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2026-115627",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-26T14:27:42.624297Z",
"version": "2.0.3"
}
}
]
},
"published": "2026-10-25T20:16:32.110",
"references": [
{
"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"url": "https://cna.erlef.org/cves/CVE-2026-115627.html"
},
{
"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"url": "https://github.com/ash-project/ash/security/advisories/GHSA-gr2r-f49c-9gm2"
},
{
"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"url": "https://github.com/ash-project/ash_postgres/commit/7115bec58678f13b1ac2fb4822a0ba1aea9dbec5"
},
{
"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"url": "https://github.com/ash-project/ash_postgres/commit/8c25c945c39a45299193fe70b09fc2fa2aacac7b"
},
{
"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"url": "https://osv.dev/vulnerability/EEF-CVE-2026-115627"
}
],
"sourceIdentifier": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-863"
}
],
"source": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"type": "Secondary"
}
]
}
},
"vulnrichment": {
"containers": {
"adp": [
{
"metrics": [
{
"other": {
"content": {
"id": "CVE-2026-115627",
"options": [
{
"Exploitation": "none"
},
{
"Automatable": "no"
},
{
"Technical Impact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2026-10-26T14:27:42.624297Z",
"version": "2.0.3"
},
"type": "ssvc"
}
}
],
"providerMetadata": {
"dateUpdated": "2026-10-26T14:32:11.459Z",
"orgId": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"shortName": "CISA-ADP"
},
"title": "CISA ADP Vulnrichment"
}
],
"cna": {
"affected": [
{
"collectionURL": "https://repo.hex.pm",
"cpes": [
"cpe:2.3:a:ash-project:ash_postgres:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"\u0027Elixir.AshPostgres.DataLayer\u0027"
],
"packageName": "ash_postgres",
"packageURL": "pkg:hex/ash_postgres",
"product": "ash_postgres",
"programFiles": [
"lib/data_layer.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:lateral_join_query/3"
},
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:through_step_queries/4"
},
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:run_query_with_lateral_join/4"
}
],
"repo": "https://github.com/ash-project/ash_postgres",
"vendor": "ash-project",
"versions": [
{
"lessThan": "2.15.2",
"status": "affected",
"version": "0.38.0",
"versionType": "semver"
}
]
},
{
"collectionURL": "https://github.com",
"cpes": [
"cpe:2.3:a:ash-project:ash_postgres:*:*:*:*:*:*:*:*"
],
"defaultStatus": "unaffected",
"modules": [
"\u0027Elixir.AshPostgres.DataLayer\u0027"
],
"packageName": "ash-project/ash_postgres",
"packageURL": "pkg:github/ash-project/ash_postgres",
"product": "ash_postgres",
"programFiles": [
"lib/data_layer.ex"
],
"programRoutines": [
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:lateral_join_query/3"
},
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:through_step_queries/4"
},
{
"name": "\u0027Elixir.AshPostgres.DataLayer\u0027:run_query_with_lateral_join/4"
}
],
"repo": "https://github.com/ash-project/ash_postgres",
"vendor": "ash-project",
"versions": [
{
"lessThan": "8c25c945c39a45299193fe70b09fc2fa2aacac7b",
"status": "affected",
"version": "7115bec58678f13b1ac2fb4822a0ba1aea9dbec5",
"versionType": "git"
}
]
}
],
"configurations": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eReachable when the join resource of a \u003ccode\u003emany_to_many\u003c/code\u003e relationship, or a resource along a \u003ccode\u003ethrough\u003c/code\u003e 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).\u003c/p\u003e"
},
{
"base64": false,
"type": "text/markdown",
"value": "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)."
}
],
"value": "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)."
}
],
"cpeApplicability": [
{
"nodes": [
{
"cpeMatch": [
{
"criteria": "cpe:2.3:a:ash-project:ash_postgres:*:*:*:*:*:*:*:*",
"versionEndExcluding": "2.15.2",
"versionStartIncluding": "0.38.0",
"vulnerable": true
}
],
"negate": false,
"operator": "OR"
}
],
"operator": "AND"
}
],
"credits": [
{
"lang": "en",
"type": "finder",
"value": "Will Townsend"
},
{
"lang": "en",
"type": "reporter",
"value": "Will Townsend"
},
{
"lang": "en",
"type": "remediation developer",
"value": "Zach Daniel / Ash Project"
}
],
"dateAssigned": "2026-10-25T17:27:14.000Z",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eIncorrect Authorization vulnerability in ash-project ash_postgres allows a user to load destination records linked to a source record only through another tenant\u0027s join rows.\u003c/p\u003e\n\u003cp\u003eWhen a \u003ccode\u003emany_to_many\u003c/code\u003e relationship, or a \u003ccode\u003ethrough\u003c/code\u003e relationship, is loaded with a lateral join (for example with a per-record limit or sort), \u003ccode\u003eAshPostgres.DataLayer\u003c/code\u003e builds the query for the join resource, and for each resource along a \u003ccode\u003ethrough\u003c/code\u003e path, in \u003ccode\u003elateral_join_query/3\u003c/code\u003e and \u003ccode\u003ethrough_step_queries/4\u003c/code\u003e without running that resource\u0027s read action, which is where attribute multitenancy is applied. When those resources use \u003ccode\u003estrategy :attribute\u003c/code\u003e multitenancy, rows belonging to other tenants were joined, so the load returned destination records that the caller\u0027s tenant is not related to.\u003c/p\u003e\n\u003cp\u003eThis issue affects ash_postgres: from 0.38.0 before 2.15.2.\u003c/p\u003e"
},
{
"base64": false,
"type": "text/markdown",
"value": "Incorrect Authorization vulnerability in ash-project ash_postgres allows a user to load destination records linked to a source record only through another tenant\u0027s join rows.\n\nWhen 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\u0027s 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\u0027s tenant is not related to.\n\nThis issue affects ash_postgres: from 0.38.0 before 2.15.2."
}
],
"value": "Incorrect Authorization vulnerability in ash-project ash_postgres allows a user to load destination records linked to a source record only through another tenant\u0027s join rows.\n\nWhen 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\u0027s 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\u0027s tenant is not related to.\n\nThis issue affects ash_postgres: from 0.38.0 before 2.15.2."
}
],
"impacts": [
{
"capecId": "CAPEC-1",
"descriptions": [
{
"lang": "en",
"supportingMedia": [
{
"base64": false,
"type": "text/html",
"value": "\u003cp\u003eA user of one tenant loading a many_to_many or through relationship receives destination records linked only through another tenant\u0027s join rows.\u003c/p\u003e"
},
{
"base64": false,
"type": "text/markdown",
"value": "A user of one tenant loading a many_to_many or through relationship receives destination records linked only through another tenant\u0027s join rows."
}
],
"value": "A user of one tenant loading a many_to_many or through relationship receives destination records linked only through another tenant\u0027s join rows."
}
]
}
],
"metrics": [
{
"cvssV4_0": {
"Automatable": "NOT_DEFINED",
"Recovery": "NOT_DEFINED",
"Safety": "NOT_DEFINED",
"attackComplexity": "LOW",
"attackRequirements": "PRESENT",
"attackVector": "NETWORK",
"baseScore": 6,
"baseSeverity": "MEDIUM",
"privilegesRequired": "LOW",
"providerUrgency": "NOT_DEFINED",
"subAvailabilityImpact": "NONE",
"subConfidentialityImpact": "NONE",
"subIntegrityImpact": "NONE",
"userInteraction": "NONE",
"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",
"version": "4.0",
"vulnAvailabilityImpact": "NONE",
"vulnConfidentialityImpact": "HIGH",
"vulnIntegrityImpact": "NONE",
"vulnerabilityResponseEffort": "NOT_DEFINED"
},
"format": "CVSS",
"scenarios": [
{
"lang": "en",
"value": "GENERAL"
}
]
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-863",
"description": "CWE-863 Incorrect Authorization",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-25T19:49:50.510Z",
"orgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"shortName": "EEF"
},
"references": [
{
"name": "AshPostgres ignores attribute multitenancy on the join resource when loading `many_to_many` and `through` relationships, returning records related through other tenants\u0027 rows",
"tags": [
"vendor-advisory",
"related"
],
"url": "https://github.com/ash-project/ash/security/advisories/GHSA-gr2r-f49c-9gm2"
},
{
"name": "EEF CNA record for CVE-2026-115627",
"tags": [
"related"
],
"url": "https://cna.erlef.org/cves/CVE-2026-115627.html"
},
{
"name": "OSV record EEF-CVE-2026-115627",
"tags": [
"related"
],
"url": "https://osv.dev/vulnerability/EEF-CVE-2026-115627"
},
{
"name": "Introducing commit 7115bec in ash-project/ash_postgres",
"tags": [
"related"
],
"url": "https://github.com/ash-project/ash_postgres/commit/7115bec58678f13b1ac2fb4822a0ba1aea9dbec5"
},
{
"name": "Fix commit 8c25c94 in ash-project/ash_postgres",
"tags": [
"patch"
],
"url": "https://github.com/ash-project/ash_postgres/commit/8c25c945c39a45299193fe70b09fc2fa2aacac7b"
}
],
"source": {
"discovery": "EXTERNAL"
},
"title": "AshPostgres ignores attribute multitenancy on the join resource when loading many_to_many and through relationships, returning records related through other tenants\u0027 rows"
}
},
"cveMetadata": {
"assignerOrgId": "6b3ad84c-e1a6-4bf7-a703-f496b71e49db",
"assignerShortName": "EEF",
"cveId": "CVE-2026-115627",
"datePublished": "2026-10-25T19:49:50.510Z",
"dateReserved": "2026-10-23T13:00:02.154Z",
"dateUpdated": "2026-10-26T14:35:21.109Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2"
}
}
}
Loading…
Loading…
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Experimental. This forecast is provided for visualization only and may change without notice. Do not use it for operational decisions.
Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
Loading timeline…
Loading…
Loading…
The MITRE ATT&CK techniques below are AI-generated suggestions, inferred from the description of the
vulnerability by the CIRCL/vulnerability-attack-technique-classification-roberta-base
model, served locally by ML-Gateway.
They have not been verified by an analyst and are provided for guidance only.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Loading…
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.