CVE-2026-33872: Nodejs Elixir-nodejs Has Cross-User Data Leakage Vulnerability

HIGH
Advisory Identifier: GHSA-rwcr-rpcc-3g9m
CWE-362
Published
Advisory Summary

CVE-2026-33872 is a HIGH elixir-nodejs has cross-user data leakage vulnerability (CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')) affecting Nodejs libraries in the Hex ecosystem. The issue involves elixir-nodejs has cross-user data leakage or information disclosure due to worker protocol race condition. Remediation is available by upgrading affected packages to version 3.1.4.

CVE-2026-33872 at a Glance

CVE Identifier CVE-2026-33872
GHSA Identifier GHSA-rwcr-rpcc-3g9m
Severity HIGH
CVSS v3.1 Base Score N/A
CWE Classification CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')
Affected Product Nodejs
Package Ecosystem Hex
Published Date
Last Updated

How to Fix CVE-2026-33872

To remediate this vulnerability, upgrade all affected Nodejs dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

nodejs fixed: 3.1.4
Upgrade nodejs to 3.1.4
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for nodejs

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-33872, inspect your project dependencies for Nodejs:

inspect dependencies for nodejs

Analyze the terminal output to locate any version of Nodejs in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 3.1.4), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition'), where the product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently. In Nodejs, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Impact This vulnerability 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. ### Patches fixed in v3.1.4 ### Resources https://github.com/revelrylabs/elixir-nodejs/issues/100 https://github.com/revelrylabs/elixir-nodejs/pull/105

CVE-2026-33872 Affected Nodejs Versions

1 component(s)
Fixed Versions:
3.1.4
Product / Package Ecosystem Affected Versions Fixed Version
nodejs
Hex
< 3.1.4
3.1.4

References

Frequently Asked Questions

What is CVE-2026-33872?
CVE-2026-33872 is a security vulnerability in Nodejs involving elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition').
Which Nodejs versions are affected?
Affected versions include releases prior to 3.1.4 across affected packages: nodejs.
What version fixes CVE-2026-33872?
Upgrading to 3.1.4 (or the latest patched release for your respective branch) resolves the vulnerability.
Is nodejs affected?
Yes, nodejs is affected in releases prior to 3.1.4. Upgrade your dependency to 3.1.4 or later.
What CWE is associated with CVE-2026-33872?
CVE-2026-33872 is classified under CWE-362: Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') (The product contains a concurrent code sequence that requires temporary, exclusive access to a shared resource, but a timing window exists in which the shared resource can be modified by another code sequence operating concurrently.).
How can I check Hex dependencies for CVE-2026-33872?
Run the dependency tree command: 'inspect dependencies for nodejs'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-rwcr-rpcc-3g9m",
  "modified" : "2026-03-27T21:49:01Z",
  "published" : "2026-03-26T18:23:01Z",
  "aliases" : [ "CVE-2026-33872" ],
  "summary" : "elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition",
  "details" : "### Impact\n\nThis vulnerability results in Cross-User Data Leakage or Information Disclosure due to a race condition in the worker protocol.\n\nThe 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.\n\nIn 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.\n\nThis 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.\n\n### Patches\n\nfixed in v3.1.4\n\n### Resources\nhttps://github.com/revelrylabs/elixir-nodejs/issues/100\n\nhttps://github.com/revelrylabs/elixir-nodejs/pull/105",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Hex",
      "name" : "nodejs"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "3.1.4"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/revelrylabs/elixir-nodejs/security/advisories/GHSA-rwcr-rpcc-3g9m"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-33872"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/revelrylabs/elixir-nodejs/issues/100"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/revelrylabs/elixir-nodejs/pull/105"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/revelrylabs/elixir-nodejs"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/revelrylabs/elixir-nodejs/releases/tag/v3.1.4"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-362" ],
    "severity" : "HIGH",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-03-26T18:23:01Z",
    "nvd_published_at" : "2026-03-27T20:16:34Z"
  }
}