CVE-2026-80223
nicheCross-tenant data leak via GraphQL subscriptions in ash_graphql (Elixir)
CVE-2026-80223 is an incorrect authorization flaw (CWE-863) in the ash_graphql library that lets an authenticated subscriber of one tenant receive records belonging to another tenant over GraphQL subscriptions. The subscription resolver authorizes each notification payload in memory, and its fast path (Ash.can/3 with run_queries?: false) evaluates the read policy filter without any tenant condition because Ash applies multitenancy at query-build time, not inside the policy filter; the single-notification clause has no tenant guard at all, and the batched clause only checks the head of the notification list. As a result, a tenant-B notification routed to a tenant-A subscriber is emitted whenever the policy filter evaluates true, yielding unauthorized cross-tenant data disclosure with high confidentiality impact (CVSS 4.0: 7.1 High, network vector, low privileges). Applications are affected if they run ash_graphql 1.4.0 through before 1.11.0 and expose GraphQL subscriptions on multitenant resources. No public proof-of-concept, KEV listing, or known exploitation exists, and EPSS puts 30-day exploitation probability at a low 0.2% (16th percentile).
What to do: Upgrade ash_graphql to 1.11.0 or later, which restores tenant-scoped authorization in the subscription resolver. As an interim mitigation, ensure read policies on subscription-exposed resources include an explicit tenant condition or force a tenant-scoped read during notification authorization, and audit any multitenant resources exposed via GraphQL subscriptions for cross-tenant notification leakage.
| ash-project ash_graphql | >= 1.4.0, < 1.11.0 |
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Incorrect Authorization vulnerability in ash-project ash_graphql allows an authenticated subscriber in one tenant to receive another tenant's records over GraphQL subscriptions. The subscription resolver in AshGraphql.Graphql.Resolver authorizes each notification payload in memory: its fast path calls Ash.can/3 with run_queries?: false, which evaluates the read policy filter against the in-memory record via Ash.Expr.eval/2 and never issues a query. Ash applies multitenancy at query-build and data-layer-prefix time, not inside query.filter, so the evaluated policy carries no tenant condition and a tenant-B notification routed to a tenant-A subscriber is emitted whenever the policy filter is true. The single-notification clause has no tenant guard at all, and the batched clause checks only the head of the notification list, so non-head entries authorize purely in memory. A tenant-scoped read is reached only when filter evaluation fails. This issue affects ash_graphql: from 1.4.0 before 1.11.0.
- Weakness
- CWE-863
- Vector
- CVSS:4.0/AV:N/AC:L/AT:N/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
In the news0 stories
No ingested article mentions this CVE yet.