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

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

- **Severity:** High 7.1 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 30 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** EEF-CVE-2026-80223, GHSA-rcqc-59g2-gjg2

## 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 (Incorrect Authorization)

## Which versions are affected by CVE-2026-80223?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ash_graphql` | Hex | From 1.4.0 | 1.11.0 |

## How do I fix CVE-2026-80223?

Upgrade ash_graphql to 1.11.0 or later.

## Is CVE-2026-80223 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-80223 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-80223 exists.

Affected packages and fixed versions:
- ash_graphql (Hex): affected from 1.4.0; fixed in 1.11.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-80223/ (Markdown: https://insights.sbomify.com/CVE-2026-80223/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-80223
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-80223
- OSV: https://osv.dev/vulnerability/CVE-2026-80223

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-80223/
Summaries are generated and may contain mistakes; the official description above is the record.