Vulnerability advisory
EEF-CVE-2026-82367
Re-entrant synchronous publish in AshGraphql subscription batcher delivers one subscriber's records to another's topic
Also known as CVE-2026-82367GHSA-wm4m-cjmc-5v8c
- CVSS 4.0
CVSS:4.0/AV:N/AC:H/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 b798ef5288664a0261990b19765558f168b718fb | b798ef5288664a0261990b19765558f168b718fb |
Also listed as affected (41)
| |
Description
Summary
Exposure of Data Element to Wrong Session vulnerability in ash-project ash_graphql can deliver one subscription's resolved records to a different subscriber's topic.
AshGraphql.Subscription.Batcher.do_send/5 reads the resolved batch from the process dictionary via Process.get(:batch_resolved) and then unconditionally deletes it. That is sound only inside a task the library owns. On the :backpressure_sync and :noproc fallbacks do_send/5 runs inline in the publishing caller's process, so if a resolver inside an outer do_send/5 triggers another synchronous Ash notification, the inner call finds the outer run's value still under :batch_resolved, adopts it as its own result, and publishes it to the inner topic, a different subscription document with a different actor and tenant. It then deletes the key, so the outer run publishes nothing. The key is not namespaced by run, so records cannot be told apart. The fix saves, clears, and restores :batch_resolved around each run.
This issue affects ash_graphql: from 1.4.0 before 1.11.0.
Configurations
The application uses ash_graphql subscriptions where a subscription resolver's execution can itself emit an Ash notification, and delivery takes the synchronous :backpressure_sync or :noproc (missing-batcher) path rather than a library-owned task.