CVE-2026-81643
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
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.
Affected Software
| Vendor | Product | Version Range | Status |
|---|---|---|---|
| ash-project | ash_graphql | 1.4.0 < 1.11.0 | affected |
| ash-project | ash_graphql | 3cb2c9870d050c7c4bba6c211aaed97d732f7e81 < e8e67f39add2ce0771e6db5f086afe68ba212c57 | affected |
Weaknesses
- CWE-863: CWE-863 Incorrect Authorization
References
- https://github.com/ash-project/ash_graphql/security/advisories/GHSA-j684-hch4-q888
- https://cna.erlef.org/cves/CVE-2026-81643.html
- https://osv.dev/vulnerability/EEF-CVE-2026-81643
- https://github.com/ash-project/ash_graphql/commit/e8e67f39add2ce0771e6db5f086afe68ba212c57
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.