CVE-2026-80223
Last modified
CVE-2026-80223 is a high-severity vulnerability rated 7.1/10 on the CVSS scale. 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. EPSS estimates a 0.25% chance of exploitation in the next 30 days.
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| ash-project | ash_graphql | >= 1.4.0, < 1.11.0 |
| ash-project | ash_graphql | >= 4c377e541a2adb6befc651f3dccc6a797bc58ba9, < 6e30b8b5a04bdeaed5d7514caa6b2d056d8d993e |
References
Timeline
- Published
- Last Modified
- Status
- Deferred
Frequently Asked Questions
What is CVE-2026-80223?
How severe is CVE-2026-80223?
How do I fix CVE-2026-80223?
How Strix Helps
- Uncovering a hidden BOLA in Appsmith's snapshot logicStrix autonomously discovered a BOLA/IDOR vulnerability in Appsmith's snapshot deletion path.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-80213An issue was discovered in the resolv gem before 0.7.2 for R…4
- CVE-2026-80214LibreNMS’s Virtualization Discovery module is vulnerable to …8.6
- CVE-2026-80217Hidden functionality issue exists in FF-RFI079I4 and FF-RFI0…8.7
- CVE-2026-80218Improper Authentication vulnerability in team-alembic AshAut…7.6
- CVE-2026-80219Rejected reason: Red Hat Product Security has come to the co…
- CVE-2026-8022Inappropriate implementation in MHTML in Google Chrome prior…3.1
- CVE-2026-80225In NLnetLabs Unbound up to and including 1.26.0, a degradati…7.5
- CVE-2026-80227Incorrect Comparison vulnerability in ash-project ash_sql al…2.1
- CVE-2026-80229When performing transfers via libcurl’s multi interface, poo…7.5
- CVE-2026-8023Zephyr's HTTP server (subsys/net/lib/http) provides a static…7.5
- CVE-2026-80230When `CURLOPT_PINNEDPUBLICKEY` is configured alongside optio…7.5
- CVE-2026-80231A flaw in libcurl makes it wrongly reuse an existing HTTPS c…7.5
Are you affected by CVE-2026-80223?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST