Quick answers
- Is CVE-2026-81643 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-81643 being exploited in the wild.
- How severe is CVE-2026-81643?
- Informational severity, published 30 August 2026.
- Which products and versions are affected?
- Ash-Project Ash Graphql 1.4.0 to before 1.11.0.
- Is there a fix for CVE-2026-81643?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-81643 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-81643?
- Check whether you run Ash-Project Ash Graphql at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
This is an authorization bypass vulnerability in AshGraphql.Subscription.Batcher's do_send/5 function. The first notification in a batch is correctly filtered with should_send?/1, which blocks unauthorized results (those with forbidden, not_found errors, or no error code). However, subsequent notifications in the same batch are fetched from the process dictionary and re-run through the pipeline without applying the authorization filter before being published. With batching enabled by default and a one-second batch window, two qualifying notifications are sufficient to leak unauthorized data. The fix applies the should_send?/1 filter to the entire batch, not just the first notification.
Affected products
- ash-project ash_graphql 1.4.0 to before 1.11.0
Timeline
- 2026-08-30: disclosed