AIKIDO-2026-434532
ash_graphql is vulnerable to Improper Authorization
71
High Risk
This Affects:
ash_graphqlTL;DR
The AshGraphql subscription resolver authorizes notification payloads in memory using an Ash.can/3 check with run_queries?: false, which evaluates read-policy filters against notification records without issuing a tenant-scoped database read. The tenant guard only inspects the first entry of a batched notification. When batched notifications share authorization criteria, records belonging to one tenant can be delivered to subscribers of another tenant. The fix applies tenant enforcement to every subscription notification.
Who does this affect?
You are affected if you are using a version that falls within the vulnerable range and you use GraphQL subscriptions with multitenancy.
Background info
ash_graphql is vulnerable to Improper Authorization in versions 1.4.0 - 1.10.1.
How to fix this
Upgrade the ash_graphql library to the patch version.
Links
Other
github.com/ash-project/ash_graphql/blob/v1.11.0/CHANGELOG.md#v1110-2026-08-30
cna.erlef.org/cves/CVE-2026-80223.htmlosv.dev/vulnerability/EEF-CVE-2026-80223
Are You Affected?
Connect your repositories to instantly see whether vulnerable or malicious packages exist in your codebase.
Free. No credit card required.
I consent to receiving marketing communications based on Aikido’s Privacy Policy.
SOC 2Compliant
ISO 27001CompliantISO 42001Compliant
FedRAMPImplementing© All Intel data is openly available and commercially licensed.