CVE-2026-33872

HIGHPre-NVD 7.17.1—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 76% 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
7.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.1Exploit: None knownExposed: 0

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

elixir-nodejs provides an Elixir API for calling Node.js functions. A vulnerability in versions prior to 3.1.4 results in Cross-User Data Leakage or Information Disclosure due to a race condition in the worker protocol. The lack of request-response correlation creates a "stale response" vulnerability. Because the worker does not verify which request a response belongs to, it may return the next available data in the buffer to an unrelated caller. In high-throughput environments where the library processes sensitive user data (e.g., PII, authentication tokens, or private records), a timeout or high concurrent load can cause Data A (belonging to User A) to be returned to User B. This may lead to unauthorized information disclosure that is difficult to trace, as the application may not throw an error but instead provide "valid-looking" yet entirely incorrect and private data to the wrong session. The issue is fixed in v3.1.4.

CVSS v3
7.1
EG Score
7.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity71% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
25%
KEV
Not listed

Published

March 27, 2026

Last Modified

June 17, 2026

Advisory Details (4)

Auto-updated Aug 3, 2026
Patch available. Sources: github_pr, github_release, github.
github Patch Available

Information Disclosure Vulnerability in elixir-nodejs Worker Communication · Advisory · revelrylabs/elixir-nodejs · GitHub

Affected: v3.1.4

https://github.com/revelrylabs/elixir-nodejs/security/advisories/GHSA-rwcr-rpcc-3g9m
github_release Patch Available

V3.1.4

Patch available: revelrylabs/elixir-nodejs v3.1.4

https://github.com/revelrylabs/elixir-nodejs/releases/tag/v3.1.4
github_pr Patch Available

Fix response cross-contamination via request-response correlation UIDs

Patch available: revelrylabs/elixir-nodejs v3.1.4 (PR #105 merged 2026-03-23)

https://github.com/revelrylabs/elixir-nodejs/pull/105
generic

Timed-out calls can result in out-of-order responses for subsequent calls · Issue #100 · revelrylabs/elixir-nodejs · GitHub

https://github.com/revelrylabs/elixir-nodejs/issues/100

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFixed inDependents
nodejs0.1.0 ... 3.1.3 (13 versions)3.1.4—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 7× in last 7d / 28× 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-18 19:28 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-15 03:11 UTCEPSS rescore
  7. 2026-09-13 16:47 UTCEPSS rescore
  8. 2026-09-12 15:01 UTCEPSS rescore
  9. 2026-09-11 14:53 UTCEPSS rescore
  10. 2026-09-11 09:37 UTCEPSS rescore
  11. 2026-09-10 09:34 UTCEPSS rescore
  12. 2026-09-08 22:00 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 14:12 UTCEPSS rescore
  16. 2026-09-02 13:04 UTCOSV refresh
  17. 2026-09-01 13:53 UTCEPSS rescore
  18. 2026-09-01 04:39 UTCEPSS rescore
  19. 2026-09-01 04:39 UTCEPSS rescore
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 38 more
  1. 2026-08-24 14:17 UTCEPSS rescore
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 09:57 UTCEG score recompute
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 01:30 UTCEPSS rescore
  13. 2026-08-14 06:16 UTCEG score recompute
  14. 2026-08-13 22:00 UTCEPSS rescore
  15. 2026-08-12 20:34 UTCEG score recompute
  16. 2026-08-12 13:50 UTCEPSS rescore
  17. 2026-08-11 20:43 UTCEG score recompute
  18. 2026-08-11 03:46 UTCEG score recompute
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-09 17:24 UTCEG score recompute
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-09 05:49 UTCEG score recompute
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-08 03:51 UTCEG score recompute
  25. 2026-08-06 18:40 UTCEG score recompute
  26. 2026-08-06 13:46 UTCEPSS rescore
  27. 2026-08-06 00:45 UTCEG score recompute
  28. 2026-08-05 19:17 UTCEPSS rescore
  29. 2026-08-04 15:10 UTCEPSS rescore
  30. 2026-08-04 10:38 UTCEPSS rescore
  31. 2026-08-03 23:07 UTCEG score recompute
  32. 2026-08-03 10:36 UTCEPSS rescore
  33. 2026-08-02 15:10 UTCEG score recompute
  34. 2026-08-02 02:27 UTCEPSS rescore
  35. 2026-08-01 04:16 UTCEPSS rescore
  36. 2026-07-30 16:28 UTCEPSS rescore
  37. 2026-07-30 01:30 UTCEPSS rescore
  38. 2026-07-27 14:19 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-33872?
CVE-2026-33872 is a high vulnerability published on March 27, 2026. elixir-nodejs provides an Elixir API for calling Node.js functions. A vulnerability in versions prior to 3.1.4 results in Cross-User Data Leakage or Information Disclosure due to a race condition in the worker protocol. The lack of request-response correlation creates a "stale response"…
When was CVE-2026-33872 disclosed?
CVE-2026-33872 was first published in the National Vulnerability Database on March 27, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-33872 actively exploited?
CVE-2026-33872 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 75.4% of all scored CVEs.
What is the CVSS score of CVE-2026-33872?
CVE-2026-33872 has a CVSS v3 base score of 7.1 (NVD).
How do I remediate CVE-2026-33872?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-33872, 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-33872

Explore →

Is Your Infrastructure Affected by CVE-2026-33872?

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

Start Free Scan →Browse All CVEs