Vulnerability Database · npm · flowise · Version

flowise 3.1.3

3.1.3 is affected by 21 vulnerabilities.

The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 3.1.4.

Critical 5 High 7 Medium 9 Low 0 Unrated 0

Released 25 Jun 2026 Licence non-standard Also known from other sources 1 Newer releases 104 Database updated 23/Oct/2026

Release and licence data published by the npm registry. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Vulnerabilities affecting this version

flowise 3.1.3 vulnerabilities

21 vulnerabilities cover flowise 3.1.3. Scroll the table for all of them, or open the full list in the database.

Vulnerability Severity Fixed version Disclosed
Critical Remote Code Execution Vulnerability in Flowise Package 10.0 critical No fix published 14 Mar 2025
CVE-2025-55346: Flowise Vulnerable to Remote Code Execution via Dynamic Function Constructor Injection 9.8 critical No fix published 06 Oct 2025
CVE-2025-8943: Flowise Remote Code Execution Vulnerability Due to Lack of Authentication 9.8 critical No fix published 14 Aug 2025
CVE-2025-55346: Flowise JS Injection Remote Code Execution Vulnerability 9.8 critical No fix published 14 Aug 2025
Critical Pre-auth Arbitrary File Upload Vulnerability in Flowise 9.3 critical No fix published 13 Mar 2025
Arbitrary File Upload Vulnerability in FlowiseAI Flowise v2.2.6 8.9 high No fix published 05 Mar 2025
Authentication Bypass Vulnerability in Flowise 3.0.1 via Unprotected Registration Endpoint 8.7 high No fix published 17 Nov 2025
File Upload Vulnerability in Flowise Package Leading to Remote Code Execution 8.3 high No fix published 08 Oct 2025
Flowise Unauthenticated Denial of Service (DoS) Vulnerability 7.5 high No fix published 27 Aug 2024
Flowise CORS Misconfiguration in packages/server/src/index.ts 7.5 high No fix published 05 Aug 2024
CVE-2024-36420: Flowise Path Injection in npm/flowise 7.5 high No fix published 05 Aug 2024
Flowise Authentication Bypass Vulnerability 7.3 high No fix published 27 Aug 2024
Unauthorized Access to Private Chatflow TTS Credentials in Flowise 6.3 medium 3.1.4 04 Aug 2026
Critical XSS Vulnerability in Flowise Package 6.3 medium No fix published 03 Oct 2025
CVE-2024-37146: Flowise Cross-site Scripting in /api/v1/credentials/id 6.1 medium No fix published 05 Aug 2024
CVE-2024-36423: Flowise Cross-site Scripting in /api/v1/public-chatflows/id 6.1 medium No fix published 05 Aug 2024
CVE-2024-37145: Flowise Cross-site Scripting in /api/v1/chatflows-streaming/id 6.1 medium No fix published 05 Aug 2024
CVE-2024-36422: Flowise Cross-site Scripting in api/v1/chatflows/id 6.1 medium No fix published 05 Aug 2024
SQL Injection Vulnerability in FlowiseDB: Authenticated User Exploitation 5.9 medium No fix published 07 Apr 2025
Stored XSS Vulnerability in Flowise: Potential Credential Theft via Chat Logs 5.3 medium No fix published 03 Oct 2025
CVE-2026-8026: Flowise Bcrypt Password Hash Exposure Vulnerability 3.7 medium No fix published 06 May 2026

Looking for another version, or everything Vulert holds for flowise?

All versions → Full vulnerability list →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About flowise 3.1.3

Is flowise 3.1.3 vulnerable?

Yes. 21 vulnerabilities in the Vulert database cover flowise 3.1.3: 5 critical, 7 high, 9 medium and 0 low. The upgrade Vulert recommends is 3.1.4, and each entry above names the fixed version to move to.

Which version of flowise should I use instead of 3.1.3?

3.1.4 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 3.1.3 the latest release of flowise?

No. 3.1.3 was published 25 Jun 2026, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

How do I monitor flowise for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the flowise version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.