PT-2026-83628 · Unknown · Ash Graphql

·

CVE-2026-82367

·

Published

2026-08-30

·

Updated

2026-09-01

CVSS v4.0

2.3

Low

VectorAV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Name of the Vulnerable Software and Affected Versions ash graphql versions 1.4.0 through 1.10.x
Description An issue exists where resolved records from one subscription may be delivered to a different subscriber's topic. This occurs because the do send/5 function in AshGraphql.Subscription.Batcher retrieves the resolved batch from the process dictionary using Process.get(:batch resolved) and deletes it unconditionally. When using :backpressure sync or :noproc fallbacks, do send/5 runs inline. If a resolver within an outer do send/5 call triggers another synchronous Ash notification, the inner call retrieves the outer run's value from :batch resolved, publishes it to the inner topic (which may belong to a different actor or tenant), and deletes the key, leaving the outer run with nothing to publish.
Recommendations Update ash graphql to version 1.11.0 or later.

Exploit

Fix

Found an issue in the description? Have something to add? Feel free to write us 👾

Weakness Enumeration

Related Identifiers

CVE-2026-82367
GHSA-WM4M-CJMC-5V8C

Affected Products

Ash Graphql