{"affected":[{"package":{"ecosystem":"Hex","name":"ash_graphql","purl":"pkg:hex/ash_graphql"},"ranges":[{"events":[{"introduced":"1.4.0"},{"fixed":"1.11.0"}],"type":"SEMVER"}],"versions":["1.4.0","1.4.1","1.4.2","1.4.3","1.4.4","1.4.5","1.4.6","1.4.7","1.5.0","1.5.1","1.6.0","1.7.0","1.7.1","1.7.2","1.7.3","1.7.4","1.7.5","1.7.6","1.7.7","1.7.8","1.7.9","1.7.10","1.7.11","1.7.12","1.7.13","1.7.14","1.7.15","1.7.16","1.7.17","1.8.0","1.8.1","1.8.2","1.8.3","1.8.4","1.8.5","1.9.0","1.9.1","1.9.2","1.9.3","1.9.4","1.10.0","1.10.1"]},{"ranges":[{"events":[{"introduced":"4c377e541a2adb6befc651f3dccc6a797bc58ba9"},{"fixed":"6e30b8b5a04bdeaed5d7514caa6b2d056d8d993e"}],"repo":"https://github.com/ash-project/ash_graphql","type":"GIT"}]}],"aliases":["GHSA-rcqc-59g2-gjg2","CVE-2026-80223"],"credits":[{"name":"Peter Ullrich","type":"FINDER"},{"name":"Peter Ullrich","type":"REPORTER"},{"name":"Zach Daniel / Ash Project","type":"REMEDIATION_DEVELOPER"},{"name":"Jonatan Männchen / EEF","type":"COORDINATOR"}],"database_specific":{"capec_ids":["CAPEC-1"],"cpe_ids":["cpe:2.3:a:ash-project:ash_graphql:*:*:*:*:*:*:*:*"],"cwe_ids":["CWE-863"]},"details":"## Summary\n\nIncorrect Authorization vulnerability in ash-project ash_graphql allows an authenticated subscriber in one tenant to receive another tenant's records over GraphQL subscriptions.\n\nThe 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.\n\nThis issue affects ash_graphql: from 1.4.0 before 1.11.0.\n\n## Configurations\n\nThe application exposes `ash_graphql` subscriptions on a multitenant resource whose read policy passes on in-memory filter evaluation alone, and where a notification created in one tenant can reach a subscriber scoped to another tenant.","id":"EEF-CVE-2026-80223","modified":"2026-09-08T20:15:02.207876Z","published":"2026-08-30T18:27:09.440Z","references":[{"type":"ADVISORY","url":"https://github.com/ash-project/ash_graphql/security/advisories/GHSA-rcqc-59g2-gjg2"},{"type":"WEB","url":"https://cna.erlef.org/cves/CVE-2026-80223.html"},{"type":"FIX","url":"https://github.com/ash-project/ash_graphql/commit/6e30b8b5a04bdeaed5d7514caa6b2d056d8d993e"},{"type":"PACKAGE","url":"https://hex.pm/packages/ash_graphql"}],"related":[],"schema_version":"1.7.3","severity":[{"score":"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","type":"CVSS_V4"}],"summary":"Cross-tenant subscription disclosure in AshGraphql authorizes notifications in memory without a tenant-scoped read","upstream":[]}