<?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>Sun, 04 Oct 2026 10:21:55 +0000</lastBuildDate>
    <item>
      <title>bdu:2022-05540</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2022-05540</link>
      <description>bdu:2022-05540</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2022-05540</guid>
    </item>
    <item>
      <title>EUVD-2026-233776</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-233776</link>
      <description>EUVD-2026-233776</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-233776</guid>
    </item>
    <item>
      <title>fkie_cve-2022-36045</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2022-36045</link>
      <description>&lt;p&gt;NodeBB Forum Software is powered by Node.js and supports either Redis, MongoDB, or a PostgreSQL database. It utilizes web sockets for instant interactions and real-time notifications. `utils.generateUUID`, a helper function available in essentially all versions of NodeBB (as far back as v1.0.1 and potentially earlier) used a cryptographically insecure Pseudo-random number generator (`Math.random()`), which meant that a specially crafted script combined with multiple invocations of the password reset functionality could enable an attacker to correctly calculate the reset code for an account they do not have access to. This vulnerability impacts all installations of NodeBB. The vulnerability allows for an attacker to take over any account without the involvement of the victim, and as such, the remediation should be applied immediately (either via NodeBB upgrade or cherry-pick of the specific changeset. The vulnerability has been patched in version 2.x and 1.19.x. There is no known workaround, but the patch sets listed above will fully patch the vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;NodeBB Forum Software is powered by Node.js and supports either Redis, MongoDB, or a PostgreSQL database. It utilizes web sockets for instant interactions and real-time notifications. `utils.generateUUID`, a helper function available in essentially all versions of NodeBB (as far back as v1.0.1 and potentially earlier) used a cryptographically insecure Pseudo-random number generator (`Math.random()`), which meant that a specially crafted script combined with multiple invocations of the password reset functionality could enable an attacker to correctly calculate the reset code for an account they do not have access to. This vulnerability impacts all installations of NodeBB. The vulnerability allows for an attacker to take over any account without the involvement of the victim, and as such, the remediation should be applied immediately (either via NodeBB upgrade or cherry-pick of the specific changeset. The vulnerability has been patched in version 2.x and 1.19.x. There is no known workaround, but the patch sets listed above will fully patch the vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2022-36045</guid>
    </item>
    <item>
      <title>GHSA-p4cc-w597-6cpm — Cryptographically weak PRNG in `utils.generateUUID`</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-p4cc-w597-6cpm</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nodebb&lt;/p&gt;
&lt;p&gt;### In Brief
`utils.generateUUID`, a helper function available in essentially all versions of NodeBB (as far back as v1.0.1 and potentially earlier) used a cryptographically insecure Pseudo-random number generator (`Math.random()`), which meant that a specially crafted script combined with multiple invocations of the password reset functionality could enable an attacker to correctly calculate the reset code for an account they do not have access to.&lt;/p&gt;
&lt;p&gt;### Impact
This vulnerability impacts all installations of NodeBB. The vulnerability allows for an attacker to take over any account without the involvement of the victim, and as such, the remediation should be applied immediately (either via NodeBB upgrade or cherry-pick of the specific changeset. Patches have been provided for both active branches of NodeBB (v2.x and v1.19.x)—please see below.&lt;/p&gt;
&lt;p&gt;If you are already on v2.0.0 or v1.19.7, you can upgrade with no ill effects. The new version contains only the patch for this vulnerability.&lt;/p&gt;
&lt;p&gt;The impact of this vulnerability is slightly lessened by the requirement that the target&amp;#39;s email address must be known, **and** user emails are protected values in NodeBB. However, since NodeBB can be configured to display email addresses if the admin so wishes, and as email addresses can often by derived from other sources and/or guessed, the impact of this vulnerability is still fairly high.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;#### v2.x
The vulnerability has been patched in https://github.com/NodeBB/NodeBB/commit/e8…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: nodebb&lt;/p&gt;
&lt;p&gt;### In Brief
`utils.generateUUID`, a helper function available in essentially all versions of NodeBB (as far back as v1.0.1 and potentially earlier) used a cryptographically insecure Pseudo-random number generator (`Math.random()`), which meant that a specially crafted script combined with multiple invocations of the password reset functionality could enable an attacker to correctly calculate the reset code for an account they do not have access to.&lt;/p&gt;
&lt;p&gt;### Impact
This vulnerability impacts all installations of NodeBB. The vulnerability allows for an attacker to take over any account without the involvement of the victim, and as such, the remediation should be applied immediately (either via NodeBB upgrade or cherry-pick of the specific changeset. Patches have been provided for both active branches of NodeBB (v2.x and v1.19.x)—please see below.&lt;/p&gt;
&lt;p&gt;If you are already on v2.0.0 or v1.19.7, you can upgrade with no ill effects. The new version contains only the patch for this vulnerability.&lt;/p&gt;
&lt;p&gt;The impact of this vulnerability is slightly lessened by the requirement that the target&amp;#39;s email address must be known, **and** user emails are protected values in NodeBB. However, since NodeBB can be configured to display email addresses if the admin so wishes, and as email addresses can often by derived from other sources and/or guessed, the impact of this vulnerability is still fairly high.&lt;/p&gt;
&lt;p&gt;### Patches&lt;/p&gt;
&lt;p&gt;#### v2.x
The vulnerability has been patched in https://github.com/NodeBB/NodeBB/commit/e8…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-p4cc-w597-6cpm</guid>
    </item>
    <item>
      <title>gsd-2022-36045</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2022-36045</link>
      <description>gsd-2022-36045</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2022-36045</guid>
    </item>
  </channel>
</rss>
