CVE-2026-82367

LOWPre-NVD 2.32.3—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 84% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
2.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 2.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
2.3
EG Score
2.3(medium)
EG Risk
26(Track)
EG Risk 26/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity23% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
16%
KEV
Not listed

Published

August 30, 2026

Last Modified

September 1, 2026

References (5)

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
ash_graphql1.10.0 ... 1.9.4 (42 versions)1.11.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 7× in last 7d / 25× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-17 03:35 UTCEG score recompute
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-15 03:12 UTCEPSS rescore
  6. 2026-09-15 03:12 UTCEPSS rescore
  7. 2026-09-14 02:34 UTCEG score recompute
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 01:32 UTCEG score recompute
  11. 2026-09-08 22:01 UTCEPSS rescore
  12. 2026-09-08 00:31 UTCEG score recompute
  13. 2026-09-06 13:48 UTCEPSS rescore
  14. 2026-09-05 15:31 UTCEPSS rescore
  15. 2026-09-04 23:29 UTCEG score recompute
  16. 2026-09-04 05:07 UTCEPSS rescore
  17. 2026-09-02 14:12 UTCEPSS rescore
  18. 2026-09-01 16:25 UTCEG score recompute
  19. 2026-09-01 15:56 UTCEG score recompute
  20. 2026-09-01 13:54 UTCEPSS rescore
  21. 2026-09-01 04:40 UTCEPSS rescore
  22. 2026-09-01 04:40 UTCEPSS rescore
  23. 2026-08-30 19:28 UTCEG score recompute
  24. 2026-08-30 18:25 UTCEG score recompute
  25. 2026-08-30 18:24 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-82367?
CVE-2026-82367 is a low vulnerability published on August 30, 2026. 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.dosend/5 reads the resolved batch from the process dictionary via Process.get(:batchresolved) and…
When was CVE-2026-82367 disclosed?
CVE-2026-82367 was first published in the National Vulnerability Database on August 30, 2026, with the most recent update on September 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-82367 actively exploited?
CVE-2026-82367 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 84.0% of all scored CVEs.
What is the CVSS score of CVE-2026-82367?
CVE-2026-82367 has a CVSS v3 base score of 2.3 (NVD).
How do I remediate CVE-2026-82367?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-82367, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-82367

Explore →

Is Your Infrastructure Affected by CVE-2026-82367?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs