<?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>Tue, 06 Oct 2026 22:19:06 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-329906</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-329906</link>
      <description>EUVD-2026-329906</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-329906</guid>
    </item>
    <item>
      <title>fkie_cve-2026-56272</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-56272</link>
      <description>&lt;p&gt;Flowise before 3.0.13 uses bcrypt with default salt rounds of 5, providing only 32 iterations instead of the OWASP-recommended minimum of 10 rounds. Attackers can crack password hashes approximately 30 times faster with modern GPU hardware, potentially compromising all user accounts in a database breach scenario.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Flowise before 3.0.13 uses bcrypt with default salt rounds of 5, providing only 32 iterations instead of the OWASP-recommended minimum of 10 rounds. Attackers can crack password hashes approximately 30 times faster with modern GPU hardware, potentially compromising all user accounts in a database breach scenario.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-56272</guid>
    </item>
    <item>
      <title>GHSA-x2g5-fvc2-gqvp — Flowise has Insufficient Password Salt Rounds</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-x2g5-fvc2-gqvp</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: flowise&lt;/p&gt;
&lt;p&gt;### Description
The default bcrypt salt rounds is set to 5, which is below the recommended minimum for security.&lt;/p&gt;
&lt;p&gt;### Affected Code
```
export function getHash(value: string) {
    const salt = bcrypt.genSaltSync(parseInt(process.env.PASSWORD_SALT_HASH_ROUNDS || &amp;#39;5&amp;#39;))
    return bcrypt.hashSync(value, salt)
}
```&lt;/p&gt;
&lt;p&gt;### Evidence
Using 5 salt rounds provides 2^5 = 32 iterations, which is far below the OWASP recommendation of 10 (2^10 = 1024 iterations) for bcrypt. This makes password hashes vulnerable to brute-force attacks with modern hardware.&lt;/p&gt;
&lt;p&gt;### Impact
Faster password cracking - in the event of database compromise, attackers can crack password hashes significantly faster than with proper salt rounds, potentially compromising all user accounts.&lt;/p&gt;
&lt;p&gt;### Recommendation
Increase default PASSWORD_SALT_HASH_ROUNDS to at least 10 (recommended by OWASP). Consider using 12 for better security-performance balance. Document that higher values increase login time but improve security.&lt;/p&gt;
&lt;p&gt;### Notes
The default bcrypt salt rounds is 5 (line 6), which provides only 2^5=32 iterations. OWASP recommends minimum 10 rounds (1024 iterations) for bcrypt. While configurable via PASSWORD_SALT_HASH_ROUNDS env var, the default matters because: (1) most deployments use defaults, (2) existing password hashes at 5 rounds remain vulnerable even if later increased. With modern GPUs, 5 rounds allows ~300,000 hashes/second vs ~10,000/second at 10 rounds - a 30x difference in cracking speed. In a database breac…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; npm: flowise&lt;/p&gt;
&lt;p&gt;### Description
The default bcrypt salt rounds is set to 5, which is below the recommended minimum for security.&lt;/p&gt;
&lt;p&gt;### Affected Code
```
export function getHash(value: string) {
    const salt = bcrypt.genSaltSync(parseInt(process.env.PASSWORD_SALT_HASH_ROUNDS || &amp;#39;5&amp;#39;))
    return bcrypt.hashSync(value, salt)
}
```&lt;/p&gt;
&lt;p&gt;### Evidence
Using 5 salt rounds provides 2^5 = 32 iterations, which is far below the OWASP recommendation of 10 (2^10 = 1024 iterations) for bcrypt. This makes password hashes vulnerable to brute-force attacks with modern hardware.&lt;/p&gt;
&lt;p&gt;### Impact
Faster password cracking - in the event of database compromise, attackers can crack password hashes significantly faster than with proper salt rounds, potentially compromising all user accounts.&lt;/p&gt;
&lt;p&gt;### Recommendation
Increase default PASSWORD_SALT_HASH_ROUNDS to at least 10 (recommended by OWASP). Consider using 12 for better security-performance balance. Document that higher values increase login time but improve security.&lt;/p&gt;
&lt;p&gt;### Notes
The default bcrypt salt rounds is 5 (line 6), which provides only 2^5=32 iterations. OWASP recommends minimum 10 rounds (1024 iterations) for bcrypt. While configurable via PASSWORD_SALT_HASH_ROUNDS env var, the default matters because: (1) most deployments use defaults, (2) existing password hashes at 5 rounds remain vulnerable even if later increased. With modern GPUs, 5 rounds allows ~300,000 hashes/second vs ~10,000/second at 10 rounds - a 30x difference in cracking speed. In a database breac…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-x2g5-fvc2-gqvp</guid>
    </item>
  </channel>
</rss>
