Is CVE-2026-82367 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-82367 being exploited in the wild.

How severe is CVE-2026-82367?

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-82367?

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-82367 attacked?

It is attacked with local access, in a software library.

Am I affected by CVE-2026-82367?

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.

CVE-2026-82367: ash-project ash_graphql cross-session data exposure in subscriptions

CVE-2026-82367 · Severity: info · Published 2026-08-30

ash_graphql is a GraphQL library for the Ash framework used to build data APIs. A flaw in its subscription batching mechanism can cause resolved records from one subscription to be incorrectly delivered to a different subscriber's subscription topic, exposing data to the wrong user. This occurs when multiple subscriptions are processed concurrently with synchronous notifications.

Technologies: Ash-Project Ash Graphql. Vendors: Ash-Project.

Quick answers

Is CVE-2026-82367 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-82367 being exploited in the wild.
How severe is CVE-2026-82367?: 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-82367?: 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-82367 attacked?: It is attacked with local access, in a software library.
Am I affected by CVE-2026-82367?: 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

The vulnerability is a process-dictionary state management error in AshGraphql.Subscription.Batcher.do_send/5. The function reads and unconditionally deletes a batch from Process.get(:batch_resolved) without namespacing by run ID. When do_send/5 runs inline in the publishing caller's process (on :backpressure_sync and :noproc fallbacks) and a resolver triggers a nested synchronous Ash notification, the inner call mistakenly reads and adopts the outer run's batch value, publishing it to the wrong subscription topic with different actor and tenant context. The fix saves, clears, and restores :batch_resolved around each run to isolate state. Affected versions: 1.4.0 to before 1.11.0. No exploitation in the wild reported.

Affected products

ash-project ash_graphql 1.4.0 to before 1.11.0

Timeline

2026-08-30: disclosed
2026-08-30: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.