CVE-2026-81643
Received Received - Intake

Incorrect Authorization in AshGraphQL Delivers Unauthorized GraphQL Subscriptions

Publication date: 2026-08-30

Last updated on: 2026-08-30

Assigner: EEF

Description
Incorrect Authorization vulnerability in ash-project ash_graphql delivers GraphQL subscription payloads for records a subscriber is not authorized to see. In AshGraphql.Subscription.Batcher, do_send/5 resolves the first notification of a batch and filters it with should_send?/1, which drops results whose errors are coded forbidden or not_found or carry no code, precisely so that unauthorized results are not disclosed. The remaining notifications in the batch are read from the process dictionary, re-run through the pipeline, and appended to the outgoing results without that filter. They reach pubsub.publish_subscription/2, and the not is_nil(record) guard drops only nil records, not error-carrying results. Any two qualifying notifications arriving within the default one-second batch interval suffice, and batching is the default path. The fix applies should_send?/1 to the whole batch. This issue affects ash_graphql: from 1.4.0 before 1.11.0.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-30
Last Modified
2026-08-30
Generated
2026-08-31
AI Q&A
2026-08-30
EPSS Evaluated
N/A
NVD
CVE-2026-81643
EUVD
EUVD-2026-68284

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
ash-project ash_graphql From 1.4.0 (inc) to 1.11.0 (exc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-863 The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-81643 is an Incorrect Authorization vulnerability in the ash_graphql library affecting versions 1.4.0 to before 1.11.0. It allows unauthorized access to GraphQL subscription payloads due to improper authorization filtering in batch processing. The system filters the first notification in a batch but fails to apply the same filter to subsequent notifications, potentially exposing records to unauthorized subscribers.

Detection Guidance

To detect this vulnerability, check if your system runs ash_graphql versions between 1.4.0 and 1.11.0. Use commands like 'mix deps' in Elixir projects or inspect dependency files for ash_graphql. Look for GraphQL subscriptions with Ash authorization enabled that batch notifications.

Impact Analysis

This vulnerability could allow unauthorized users to receive GraphQL subscription payloads containing records they are not permitted to access. Sensitive information such as record existence, timing, and identifiers embedded in error messages may be exposed. The impact is limited to confidentiality and requires batching of at least two notifications within one second.

Compliance Impact

This vulnerability may lead to unauthorized data exposure, which could violate compliance requirements such as GDPR's data protection principles or HIPAA's access controls. Unauthorized access to sensitive records could result in regulatory penalties or breaches of confidentiality obligations.

Mitigation Strategies

Upgrade ash_graphql to version 1.11.0 or later immediately. If upgrading is not possible, disable GraphQL subscriptions or batching in your configuration. Review subscription payloads to ensure unauthorized records are not exposed.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-81643. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart