Vulnerability advisory
EEF-CVE-2026-81643
Broken access control in AshGraphql subscription batcher applies authorization suppression to only the first notification
Also known as CVE-2026-81643GHSA-j684-hch4-q888
- CVSS 4.0
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Affected versions
| Affected | Fixed in |
|---|---|
1.4.0 to before 1.11.0 | 1.11.0Advisories → |
Repository
| Affected commits | Fixed by commit |
|---|---|
| GIT github.com/ash-project/ash_graphql ↗ | |
| 3cb2c9870d050c7c4bba6c211aaed97d732f7e81 to before e8e67f39add2ce0771e6db5f086afe68ba212c57 | e8e67f39add2ce0771e6db5f086afe68ba212c57 |
Also listed as affected (41)
| |
Description
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.
Configurations
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).