Skip to content
Connect AISign inSign up free
CVE-2026-802237.1HighCWE-863

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

ash-project · ash_graphql

Fixed in 1.11.0 · Affected: ash-project ash_graphql before 1.11.0 · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.4%probability of exploitation in the next 30 days
37th percentile
050100

Higher than 37% of scored CVEs

7.1HighCVSS 4.0
LowHigh

DescriptionCVE.org

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.

Affected products2

From the CVE record. A product or version that is not listed is unknown, not unaffected.

  • ash-project · ash_graphqlfrom 1.4.0 before 1.11.0
  • ash-project · ash_graphqlVersions not stated

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas
Exploitation
Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV
Not listed
Public check
No public nuclei template
Published
August 2026

CoverageNo articles yet

No CyberSIXT article names CVE-2026-80223 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.

References