nodejs
An Elixir API for calling Node.js functions
View on Github
Activity
- Latest release
- 5d ago
- Total releases
- 15
- Cadence
- ~3 months
- Last 12 months
- 2
Reach
- Downloads
- 837.7k
- Stars
- 251
Details
- License
- MIT
- First release
- Aug 01, 2018
| Version | Released | |
|---|---|---|
3.2.0
minor
| ||
3.1.4
patch
| ||
3.1.3
patch
1 CVE
CVE-2026-33872
GHSA-rwcr-rpcc-3g9m
Mar 26, 2026
elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition
High
Network
Low
Low
None
ImpactThis 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. Patchesfixed in v3.1.4 Resourceshttps://github.com/revelrylabs/elixir-nodejs/issues/100 https://github.com/revelrylabs/elixir-nodejs/pull/105 Affected versions
0.1.0
0.2.0
0.2.1
0.2.2
0.2.3
1.0.0
1.1.0
2.0.0
3.0.0
3.1.0
3.1.1
3.1.2
+ 1 more Show less
3.1.3
Fixed in
3.1.4
References
Updated Mar 27, 2026 · Source: OSV.dev | ||
3.1.2
patch
1 CVE
CVE-2026-33872
GHSA-rwcr-rpcc-3g9m
Mar 26, 2026
elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition
High
Network
Low
Low
None
ImpactThis 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. Patchesfixed in v3.1.4 Resourceshttps://github.com/revelrylabs/elixir-nodejs/issues/100 https://github.com/revelrylabs/elixir-nodejs/pull/105 Affected versions
0.1.0
0.2.0
0.2.1
0.2.2
0.2.3
1.0.0
1.1.0
2.0.0
3.0.0
3.1.0
3.1.1
3.1.2
+ 1 more Show less
3.1.3
Fixed in
3.1.4
References
Updated Mar 27, 2026 · Source: OSV.dev | ||
3.1.1
patch
1 CVE
CVE-2026-33872
GHSA-rwcr-rpcc-3g9m
Mar 26, 2026
elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition
High
Network
Low
Low
None
ImpactThis 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. Patchesfixed in v3.1.4 Resourceshttps://github.com/revelrylabs/elixir-nodejs/issues/100 https://github.com/revelrylabs/elixir-nodejs/pull/105 Affected versions
0.1.0
0.2.0
0.2.1
0.2.2
0.2.3
1.0.0
1.1.0
2.0.0
3.0.0
3.1.0
3.1.1
3.1.2
+ 1 more Show less
3.1.3
Fixed in
3.1.4
References
Updated Mar 27, 2026 · Source: OSV.dev | ||
3.1.0
minor
1 CVE
CVE-2026-33872
GHSA-rwcr-rpcc-3g9m
Mar 26, 2026
elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition
High
Network
Low
Low
None
ImpactThis 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. Patchesfixed in v3.1.4 Resourceshttps://github.com/revelrylabs/elixir-nodejs/issues/100 https://github.com/revelrylabs/elixir-nodejs/pull/105 Affected versions
0.1.0
0.2.0
0.2.1
0.2.2
0.2.3
1.0.0
1.1.0
2.0.0
3.0.0
3.1.0
3.1.1
3.1.2
+ 1 more Show less
3.1.3
Fixed in
3.1.4
References
Updated Mar 27, 2026 · Source: OSV.dev | ||
3.0.0
major
1 CVE
CVE-2026-33872
GHSA-rwcr-rpcc-3g9m
Mar 26, 2026
elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition
High
Network
Low
Low
None
ImpactThis 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. Patchesfixed in v3.1.4 Resourceshttps://github.com/revelrylabs/elixir-nodejs/issues/100 https://github.com/revelrylabs/elixir-nodejs/pull/105 Affected versions
0.1.0
0.2.0
0.2.1
0.2.2
0.2.3
1.0.0
1.1.0
2.0.0
3.0.0
3.1.0
3.1.1
3.1.2
+ 1 more Show less
3.1.3
Fixed in
3.1.4
References
Updated Mar 27, 2026 · Source: OSV.dev | ||
2.0.0
major
1 CVE
CVE-2026-33872
GHSA-rwcr-rpcc-3g9m
Mar 26, 2026
elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition
High
Network
Low
Low
None
ImpactThis 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. Patchesfixed in v3.1.4 Resourceshttps://github.com/revelrylabs/elixir-nodejs/issues/100 https://github.com/revelrylabs/elixir-nodejs/pull/105 Affected versions
0.1.0
0.2.0
0.2.1
0.2.2
0.2.3
1.0.0
1.1.0
2.0.0
3.0.0
3.1.0
3.1.1
3.1.2
+ 1 more Show less
3.1.3
Fixed in
3.1.4
References
Updated Mar 27, 2026 · Source: OSV.dev | ||
1.1.0
minor
1 CVE
CVE-2026-33872
GHSA-rwcr-rpcc-3g9m
Mar 26, 2026
elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition
High
Network
Low
Low
None
ImpactThis 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. Patchesfixed in v3.1.4 Resourceshttps://github.com/revelrylabs/elixir-nodejs/issues/100 https://github.com/revelrylabs/elixir-nodejs/pull/105 Affected versions
0.1.0
0.2.0
0.2.1
0.2.2
0.2.3
1.0.0
1.1.0
2.0.0
3.0.0
3.1.0
3.1.1
3.1.2
+ 1 more Show less
3.1.3
Fixed in
3.1.4
References
Updated Mar 27, 2026 · Source: OSV.dev | ||
1.0.0
major
1 CVE
CVE-2026-33872
GHSA-rwcr-rpcc-3g9m
Mar 26, 2026
elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition
High
Network
Low
Low
None
ImpactThis 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. Patchesfixed in v3.1.4 Resourceshttps://github.com/revelrylabs/elixir-nodejs/issues/100 https://github.com/revelrylabs/elixir-nodejs/pull/105 Affected versions
0.1.0
0.2.0
0.2.1
0.2.2
0.2.3
1.0.0
1.1.0
2.0.0
3.0.0
3.1.0
3.1.1
3.1.2
+ 1 more Show less
3.1.3
Fixed in
3.1.4
References
Updated Mar 27, 2026 · Source: OSV.dev | ||
0.2.3
patch
1 CVE
CVE-2026-33872
GHSA-rwcr-rpcc-3g9m
Mar 26, 2026
elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition
High
Network
Low
Low
None
ImpactThis 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. Patchesfixed in v3.1.4 Resourceshttps://github.com/revelrylabs/elixir-nodejs/issues/100 https://github.com/revelrylabs/elixir-nodejs/pull/105 Affected versions
0.1.0
0.2.0
0.2.1
0.2.2
0.2.3
1.0.0
1.1.0
2.0.0
3.0.0
3.1.0
3.1.1
3.1.2
+ 1 more Show less
3.1.3
Fixed in
3.1.4
References
Updated Mar 27, 2026 · Source: OSV.dev | ||
0.2.2
patch
1 CVE
CVE-2026-33872
GHSA-rwcr-rpcc-3g9m
Mar 26, 2026
elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition
High
Network
Low
Low
None
ImpactThis 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. Patchesfixed in v3.1.4 Resourceshttps://github.com/revelrylabs/elixir-nodejs/issues/100 https://github.com/revelrylabs/elixir-nodejs/pull/105 Affected versions
0.1.0
0.2.0
0.2.1
0.2.2
0.2.3
1.0.0
1.1.0
2.0.0
3.0.0
3.1.0
3.1.1
3.1.2
+ 1 more Show less
3.1.3
Fixed in
3.1.4
References
Updated Mar 27, 2026 · Source: OSV.dev | ||
0.2.1
patch
1 CVE
CVE-2026-33872
GHSA-rwcr-rpcc-3g9m
Mar 26, 2026
elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition
High
Network
Low
Low
None
ImpactThis 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. Patchesfixed in v3.1.4 Resourceshttps://github.com/revelrylabs/elixir-nodejs/issues/100 https://github.com/revelrylabs/elixir-nodejs/pull/105 Affected versions
0.1.0
0.2.0
0.2.1
0.2.2
0.2.3
1.0.0
1.1.0
2.0.0
3.0.0
3.1.0
3.1.1
3.1.2
+ 1 more Show less
3.1.3
Fixed in
3.1.4
References
Updated Mar 27, 2026 · Source: OSV.dev | ||
0.2.0
minor
1 CVE
CVE-2026-33872
GHSA-rwcr-rpcc-3g9m
Mar 26, 2026
elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition
High
Network
Low
Low
None
ImpactThis 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. Patchesfixed in v3.1.4 Resourceshttps://github.com/revelrylabs/elixir-nodejs/issues/100 https://github.com/revelrylabs/elixir-nodejs/pull/105 Affected versions
0.1.0
0.2.0
0.2.1
0.2.2
0.2.3
1.0.0
1.1.0
2.0.0
3.0.0
3.1.0
3.1.1
3.1.2
+ 1 more Show less
3.1.3
Fixed in
3.1.4
References
Updated Mar 27, 2026 · Source: OSV.dev | ||
0.1.0
initial
1 CVE
CVE-2026-33872
GHSA-rwcr-rpcc-3g9m
Mar 26, 2026
elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition
High
Network
Low
Low
None
ImpactThis 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. Patchesfixed in v3.1.4 Resourceshttps://github.com/revelrylabs/elixir-nodejs/issues/100 https://github.com/revelrylabs/elixir-nodejs/pull/105 Affected versions
0.1.0
0.2.0
0.2.1
0.2.2
0.2.3
1.0.0
1.1.0
2.0.0
3.0.0
3.1.0
3.1.1
3.1.2
+ 1 more Show less
3.1.3
Fixed in
3.1.4
References
Updated Mar 27, 2026 · Source: OSV.dev |