Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-80223Published 2026-08-30

CVE-2026-80223 — ash-project ash_graphql

high (derived)

As of 2026-08-30, CVE-2026-80223 is a High-severity (band derived from the CVSS v4.0 score, not stated by the CNA) vulnerability in ash-project ash_graphql, CVSS v4.0 7.1. No Threadlinqs-tracked threat campaign has been attributed to CVE-2026-80223 as of 2026-08-30; the identifier is re-checked against the Threadlinqs threat corpus on every daily ingest.

CVSS v4.0
7.1/10High (derived)
EPSS
—No EPSS score yet
CISA KEV
NoNot in the KEV catalog
Tracked threats
0None linked yet
Priority
3.6/10Threadlinqs triage score
Published
CVSS v4.0 7.1 (High, derived from score) · Priority 3.6/10 · Published 2026-08-30

Last updated:

What is CVE-2026-80223?

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.

The record classifies CVE-2026-80223 under weakness class CWE-863. 1 affected-product entry is recorded, across 1 vendor, listed below. The identifier was first published 36 days ago.

Severity and exploitation probability

CVSS v4.0 base score
7.1 — High (derived from score)
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
CISA KEV
Not listed in the CISA Known Exploited Vulnerabilities catalog
Threadlinqs priority
3.6/10 — a Threadlinqs composite of the CVSS base score, the EPSS percentile and public exploit availability
Published
2026-08-30

Is CVE-2026-80223 being exploited?

It currently carries a trending score of 30 in the Threadlinqs vulnerability feed.

Affected products and versions

How to fix CVE-2026-80223

No vendor patch reference has been recorded for CVE-2026-80223 in the tracked sources. Follow the references below for a fix, and treat the products listed above as exposed until the vendor states otherwise.

Threat activity tracking CVE-2026-80223

No threat campaign in the Threadlinqs corpus currently references CVE-2026-80223, in its CVE list or as an indicator. The linkage is recomputed from the live corpus on every daily ingest, so this section fills in as soon as a tracked campaign cites the identifier.

Sources

Enriched from CVE.org, NVD. Last verified by Threadlinqs on . This product uses the NVD API but is not endorsed or certified by the NVD.

Vendor advisory and patch

Other references