EEF-CVE-2026-81643

## Summary

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.

## Configuration

The application exposes ash\_graphql subscriptions with Ash authorization enabled, and two or more notifications are batched together within the batch interval (the default path).