Answer in brief
CVE-2026-80223 records a High severity (CVSS 7.1) vulnerability in Cross-tenant subscription disclosure in AshGraphql authorizes notifications in memory without a tenant-scoped read. The current sources do not mark it as known exploited. The current feed maps ash-project/ash_graphql (generic), ash-project/ash_graphql (generic), ash-project/ash-project/ash_graphql (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 7.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps ash-project/ash_graphql (generic), ash-project/ash_graphql (generic), ash-project/ash-project/ash_graphql (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| ash-project/ash_graphqlgeneric | >=4c377e541a2adb6befc651f3dccc6a797bc58ba9 <6e30b8b5a04bdeaed5d7514caa6b2d056d8d993e | 6e30b8b5a04bdeaed5d7514caa6b2d056d8d993e |
| ash-project/ash_graphqlgeneric | >=1.4.0 <1.11.0 | 1.11.0 |
| ash-project/ash-project/ash_graphqlgeneric | >=4c377e541a2adb6befc651f3dccc6a797bc58ba9 <6e30b8b5a04bdeaed5d7514caa6b2d056d8d993e | 6e30b8b5a04bdeaed5d7514caa6b2d056d8d993e |
Published upstream
Aug 30, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Sep 3, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Aug 30, 2026
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.
Quoted source text, attributed separately from HOL analysis.