CVE-2026-33872

HIGHPre-NVD 7.17.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This high-severity CVE scores 7.1 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (33rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
Trending — 3 sources updated this week

Also known asEUVD-2026-16791 (ENISA EUVD) · GHSA-rwcr-rpcc-3g9m (GitHub Security Advisories)Source: ENISA EUVD

7.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.4%CVSS: 7.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.1HIGHmedium confidence
EG Risk
47
EG Risk 47/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity71% × 45%
Impact severity (EG Severity): CVSS 7.1 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
0.4%
EPSS %ILE
33rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (7.1): severity, escalated by confirmed exploitation. This CVE's 7.1 is its impact severity (EG Severity), not escalated.

EG Severity
7.1 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
EG Likelihood
0.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at low or medium mission impact; Attend at high (mission-essential systems).CISA BOD 26-04: 14 days if the affected system is publicly exposed; 60 days if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

March 27, 2026

Last Modified

October 26, 2026

Advisory Details (4)

Auto-updated Aug 3, 2026
Patch available. Sources: github_pr, github_release, github.
GitHub advisoryMentions a patch (unverified)

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 pull request 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
Web page

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
erlangnodejs @ 3.1.4 (fixes < 3.1.4)—ghsa

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(1 across 1 ecosystem)
Hex(1)
PackageVulnerable rangeFix by version rangeDependents
nodejs0.1.0 ... 3.1.3 (13 versions)
  • every version up to 3.1.4: fixed in 3.1.4
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 43× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 97 of 111 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 3 repeat rows among the latest 100 are merged into the row they repeat. The 14 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-11-01 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  2. 2026-11-01 07:53 UTCGHSA enrichmentGHSA-rwcr-rpcc-3g9m · GitHub severity HIGH
  3. 2026-11-01 07:53 UTCEG score recompute
  4. 2026-10-31 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  5. 2026-10-30 16:34 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  6. 2026-10-29 16:33 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  7. 2026-10-28 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  8. 2026-10-27 20:54 UTCEG score recompute
  9. 2026-10-27 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  10. 2026-10-26 21:26 UTCEG score recompute
  11. 2026-10-26 16:31 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  12. 2026-10-25 16:32 UTCEPSS rescoreEPSS 0.4% · 33rd percentile
  13. 2026-10-25 14:34 UTCEG score recompute
  14. 2026-10-24 16:32 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  15. 2026-10-24 06:37 UTCEG score recompute
  16. 2026-10-23 16:31 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  17. 2026-10-22 16:34 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  18. 2026-10-21 16:32 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  19. 2026-10-20 16:33 UTCEPSS rescoreEPSS 0.5% · 38th percentile
  20. 2026-10-19 16:31 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  21. 2026-10-18 16:31 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  22. 2026-10-18 03:46 UTCEG score recompute
  23. 2026-10-17 16:34 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  24. 2026-10-17 15:42 UTCEG score recompute
  25. 2026-10-16 16:41 UTCEPSS rescoreEPSS 0.5% · 37th percentile
Show 72 more
  1. 2026-10-15 16:32 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  2. 2026-10-14 16:32 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  3. 2026-10-13 16:34 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  4. 2026-10-12 16:34 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  5. 2026-10-12 16:13 UTCEG score recompute
  6. 2026-10-11 19:55 UTCEG score recompute
  7. 2026-10-11 17:08 UTCEG score recompute
  8. 2026-10-11 14:35 UTCEG score recompute
  9. 2026-10-11 13:48 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  10. 2026-10-11 03:31 UTCOSV refresh
  11. 2026-10-10 20:00 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  12. 2026-10-09 20:07 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  13. 2026-10-08 17:12 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  14. 2026-10-07 23:47 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  15. 2026-10-06 15:17 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  16. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  17. 2026-10-04 23:22 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  18. 2026-10-03 14:25 UTCEPSS rescoreEPSS 0.5% · 37th percentile
  19. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.5% · 36th percentile
  20. 2026-09-30 15:03 UTCEPSS rescoreEPSS 0.5% · 36th percentile
  21. 2026-09-28 13:51 UTCEPSS rescoreEPSS 0.5% · 36th percentile
  22. 2026-09-27 13:48 UTCEPSS rescoreEPSS 0.5% · 36th percentile
  23. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.5% · 36th percentile
  24. 2026-09-26 00:26 UTCEPSS rescoreEPSS 0.5% · 36th percentile
  25. 2026-09-21 15:49 UTCOSV refresh
  26. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  27. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  28. 2026-09-17 19:30 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  29. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  30. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  31. 2026-09-15 03:11 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  32. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  33. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  34. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  35. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  36. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  37. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  38. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  39. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  40. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  41. 2026-09-02 13:04 UTCOSV refresh
  42. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  43. 2026-09-01 04:39 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  44. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  45. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  46. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  47. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  48. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  49. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  50. 2026-08-24 14:17 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  51. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  52. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  53. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  54. 2026-08-19 17:03 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  55. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  56. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  57. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  58. 2026-08-16 09:57 UTCEG score recompute
  59. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  60. 2026-08-15 01:30 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  61. 2026-08-14 06:16 UTCEG score recompute
  62. 2026-08-13 22:00 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  63. 2026-08-12 20:34 UTCEG score recompute
  64. 2026-08-12 13:50 UTCEPSS rescoreEPSS 0.3% · 24th percentile
  65. 2026-08-11 20:43 UTCEG score recompute
  66. 2026-08-11 03:46 UTCEG score recompute
  67. 2026-08-11 00:00 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  68. 2026-08-09 17:24 UTCEG score recompute
  69. 2026-08-09 13:46 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  70. 2026-08-09 05:49 UTCEG score recompute
  71. 2026-08-08 16:37 UTCEPSS rescoreEPSS 0.3% · 23rd percentile
  72. 2026-08-08 03:51 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-33872?
CVE-2026-33872 is a high-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-33872 published?
The CVE record for CVE-2026-33872 was published on March 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of October 26, 2026; the record at its source may have been updated since.
Is CVE-2026-33872 actively exploited?
CVE-2026-33872 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (33rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-33872?
CVE-2026-33872 has a CVSS base score of 7.1 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-33872?
A fix for CVE-2026-33872 is available: update to the fixed version the vendor names in its advisory.

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.

Book a Demo →Browse All CVEs