<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Fri, 09 Oct 2026 12:05:15 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-278188</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-278188</link>
      <description>EUVD-2026-278188</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-278188</guid>
    </item>
    <item>
      <title>fkie_cve-2026-33872</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-33872</link>
      <description>&lt;p&gt;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 &amp;#34;stale response&amp;#34; 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 &amp;#34;valid-looking&amp;#34; yet entirely incorrect and private data to the wrong session. The issue is fixed in v3.1.4.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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 &amp;#34;stale response&amp;#34; 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 &amp;#34;valid-looking&amp;#34; yet entirely incorrect and private data to the wrong session. The issue is fixed in v3.1.4.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-33872</guid>
    </item>
    <item>
      <title>GHSA-rwcr-rpcc-3g9m — elixir-nodejs has Cross-User Data Leakage or Information Disclosure due to Worker Protocol Race Condition</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-rwcr-rpcc-3g9m</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hex: nodejs&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;This vulnerability results in Cross-User Data Leakage or Information Disclosure due to a race condition in the worker protocol.&lt;/p&gt;
&lt;p&gt;The lack of request-response correlation creates a &amp;#34;stale response&amp;#34; 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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This may lead to unauthorized information disclosure that is difficult to trace, as the application may not throw an error but instead provide &amp;#34;valid-looking&amp;#34; yet entirely incorrect and private data to the wrong session.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;fixed in v3.1.4&lt;/p&gt;
&lt;p&gt;### Resources
https://github.com/revelrylabs/elixir-nodejs/issues/100&lt;/p&gt;
&lt;p&gt;https://github.com/revelrylabs/elixir-nodejs/pull/105&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Hex: nodejs&lt;/p&gt;
&lt;p&gt;### Impact&lt;/p&gt;
&lt;p&gt;This vulnerability results in Cross-User Data Leakage or Information Disclosure due to a race condition in the worker protocol.&lt;/p&gt;
&lt;p&gt;The lack of request-response correlation creates a &amp;#34;stale response&amp;#34; 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.&lt;/p&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;p&gt;This may lead to unauthorized information disclosure that is difficult to trace, as the application may not throw an error but instead provide &amp;#34;valid-looking&amp;#34; yet entirely incorrect and private data to the wrong session.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;fixed in v3.1.4&lt;/p&gt;
&lt;p&gt;### Resources
https://github.com/revelrylabs/elixir-nodejs/issues/100&lt;/p&gt;
&lt;p&gt;https://github.com/revelrylabs/elixir-nodejs/pull/105&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-rwcr-rpcc-3g9m</guid>
    </item>
  </channel>
</rss>
