CVE-2026-33872

elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition

Published Mar 27, 2026 CVSS 4.0 · 7.1 High EPSS < 1% KEV · Not listed
Description
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.

Analysis

AI-generated

Technical impact

A race condition in elixir-nodejs allows a stale response from the worker protocol, returning data that belongs to another user. The worker does not verify request-response correlation, so under high load or chronic timeout conditions the next available data in the buffer can be sent to an unrelated caller. The flaw can expose sensitive user information such as personally identifiable data, authentication credentials, or private records, and the denial of a clear error makes the misuse hard to trace.

Affected Systems

Revelry Labs elixir‑nodejs is affected in all versions prior to v3.1.4. Any deployments using those releases, especially those operating in high‑throughput or multi‑user environments, are at risk.

Risk and Exploitability

The issue has a CVSS score of 7.1, indicating a high risk of data compromise. The Exploit Prediction Scoring System score is not published, but the vulnerability is not listed in CISA’s KEV catalog. The attack is most likely achievable from within the application context by inducing concurrent requests or timed out operations; an adversary would need to jam traffic or exploit a busy server to trigger the race condition. Once exploited, the impact includes unauthorized disclosure of confidential data, with significant potential harm to users and the organization.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade elixir‑nodejs to v3.1.4 or later
  • Verify that the application is using the updated version and that no legacy code paths remain
  • Test the system under high concurrency to confirm that no stale responses are returned
  • Implement monitoring for unexpected data returns or anomalies in user sessions

Generated by OpenCVE AI on March 27, 2026 at 21:35 UTC.

Tracking

Sign in to view the affected projects.

Advisories

Source ID Title
Github GHSA Github GHSA GHSA-rwcr-rpcc-3g9m elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition
History
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'yes', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Revelrylabs
Revelrylabs elixir-nodejs
Vendors & Products Revelrylabs
Revelrylabs elixir-nodejs
Type Values Removed Values Added
Description 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.
Title elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition
Weaknesses CWE-362
References
Metrics cvssV4_0

{'score': 7.1, 'vector': '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'}

Weaknesses
  • CWE-362

    Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition')

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Mar 30, 2026, 6:58 PM
Reserved
Mar 24, 2026, 3:10 PM
Status
Awaiting Analysis
Published
Mar 27, 2026, 8:16 PM
Modified
Oct 26, 2026, 9:10 PM