{"answers":{"affected":"2 open source packages ship an affected version, including nodejs.","exploited":"There is no known exploitation of CVE-2026-33872 in the wild and no public exploit code.","fix":"Upgrade nodejs to 3.1.4 or later.","what":"CVE-2026-33872 is a high-severity vulnerability in revelrylabs elixir-nodejs, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-33872 and fix it if it is affected.\n\nWhat it is: CVE-2026-33872 is a high-severity vulnerability in revelrylabs elixir-nodejs, published on 27 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2026-33872 in the wild and no public exploit code.\n\nAffected packages and fixed versions:\n- nodejs (Hex): affected all versions; fixed in 3.1.4\n- nodejs (Hex): affected all versions; fixed in 3.1.4\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-33872/ (Markdown: https://insights.sbomify.com/CVE-2026-33872/index.md)","id":"CVE-2026-33872","markdown":"https://insights.sbomify.com/CVE-2026-33872/index.md","name":"CVE-2026-33872","record":{"aliases":["GHSA-rwcr-rpcc-3g9m"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"Elixir Node.js bridge","requires_auth":"low_privilege","summary":"A race condition in elixir-nodejs allows attackers to leak sensitive user data to unrelated sessions due to missing request-response correlation.","user_interaction":"not_required","vuln_class":"race_condition"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7.1,"severity":"high","source":"cna","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","version":"4.0"},"cwes":[{"id":"CWE-362","name":"Concurrent Execution using Shared Resource with Improper Synchronization"}],"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.","ecosystems":["Hex"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":true,"headline":"elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition","id":"CVE-2026-33872","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Hex","product":null,"products":[],"type":"race_condition","year":"2026"},"n_packages":2,"n_references":4,"next":{"headline":"Langflow has Authenticated Code Execution in Agentic Assistant Validation","id":"CVE-2026-33873"},"packages":[{"ecosystem":"Hex","fixed":["3.1.4"],"introduced":["0"],"last_affected":[],"package":"nodejs","purl":null,"source":"GHSA-rwcr-rpcc-3g9m"},{"ecosystem":"Hex","fixed":["3.1.4"],"introduced":["0"],"last_affected":[],"package":"nodejs","purl":"pkg:hex/nodejs","source":"GHSA-rwcr-rpcc-3g9m"}],"prev":{"headline":"Netty HTTP/2 CONTINUATION Frame Flood DoS via Zero-Byte Frame Bypass","id":"CVE-2026-33871"},"products":["elixir-nodejs"],"published":"2026-03-27","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"yes","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-30","vendors":["revelrylabs"]},"summary":"A race condition in elixir-nodejs allows attackers to leak sensitive user data to unrelated sessions due to missing request-response correlation.","url":"https://insights.sbomify.com/CVE-2026-33872/"}