CVE Feed
2.3 Low

Exposure of Data Element to Wrong Session vulnerability in ash-project ashgraphql can deliver one subscription's resolved records to a…

CVE-2026-82367

Exposure of Data Element to Wrong Session vulnerability in ash-project ashgraphql can deliver one subscription's resolved records to a different subscriber's topic. AshGraphql.Subscription.Batcher.dosend/5 reads the resolved batch from the process dictionary via Process.get(:batchresolved) and then unconditionally deletes it. That is sound only inside a task the library owns. On the :backpressuresync and :noproc fallbacks dosend/5 runs inline in the publishing caller's process, so if a resolver inside an outer dosend/5 triggers another synchronous Ash notification, the inner call finds the outer run's value still under :batchresolved, 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 :batchresolved around each run. This issue affects ashgraphql: from 1.4.0 before 1.11.0.

Assessment

CVSS
2.3 (v4.0)
Severity
Low
EPSS
0.39% chance of exploitation in the next 30 days
Known exploited
Not listed in CISA KEV
Exploit availability
Nothing found in Exploit-DB, Metasploit, Nuclei or public PoC repositories
Published
30 August 2026
Last updated
19 November 2026
Assigner
EEF

CVSS vectorCVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

At the source

References

Community proofs of concept

No community proof of concept yet. If you have one for a published vulnerability and the right to share it, add it below — it will appear here once reviewed.

Submit a proof of concept
Before you submit *

Query this programmatically

Agents can read this through the MCP endpoint, or over HTTP:

curl https://cve.zerocrew.in/api/cve/CVE-2026-82367