CVE-2026-80223 Cross-tenant subscription disclosure in AshGraphql authorizes notifications in memory without a tenant-scoped read

High 7.1 Published Updated

Authenticated users in one tenant can receive another tenant's records via GraphQL subscriptions due to missing tenant-scoped authorization checks.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-80223?

CVE-2026-80223 is a high-severity missing authorization vulnerability in ash-project ash_graphql, published on 30 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

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

Which versions are affected by CVE-2026-80223?

1 open source package ship an affected version, including ash_graphql.

PackageAffectedFixed in
ash_graphql HexFrom 1.4.01.11.0

How do I fix CVE-2026-80223?

Upgrade ash_graphql to 1.11.0 or later.

Upgrade, and check permissions on every request on the server, not only in the interface. More about Missing authorization.

Is CVE-2026-80223 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-80223 exists.

Sources

Also known as EEF-CVE-2026-80223, GHSA-rcqc-59g2-gjg2.

Is CVE-2026-80223 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free