VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

flowise: vulnerability history, versions and safety

flowise is a package in the npm ecosystem. Vulert records 118 vulnerabilities for it across 104 releases, from Apr 2024 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
118 vulnerabilities recorded C31 H63 M24
i
20 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
84 in the last 12 months

Most recent disclosure 07 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all flowise vulnerabilities

Vulert verdict on flowise 3.1.4 i

Updated on 23 Oct 2026

Careful: 3.1.4 has 20 known vulnerabilities, and 20 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 35/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Little adoption
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 3.1.4 — affected i
  • Vulnerabilities on record 118 over 2 years · 84 in the last year i
  • Latest disclosure 07 Oct 2026 i
  • Highest CVSS 10.0 i
  • With no published fix 20 i
  • Last release 2 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for flowise, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.1.4 29 Jul 2026 C5 H7 M8 non-standard No Details →
3.1.3 25 Jun 2026 C5 H7 M9 non-standard No Details →
3.1.2 14 Apr 2026 C17 H19 M11 non-standard No Details →
3.1.1 23 Mar 2026 C18 H33 M14 non-standard No Details →
3.1.0 16 Mar 2026 C18 H33 M14 non-standard No Details →
3.0.13 03 Feb 2026 C22 H48 M22 non-standard No Details →
3.0.12 05 Dec 2025 C22 H54 M24 non-standard No Details →
3.0.11 16 Nov 2025 C22 H54 M24 non-standard No Details →
3.0.10 06 Nov 2025 C22 H54 M24 non-standard No Details →
3.0.8 08 Oct 2025 C22 H55 M24 non-standard No Details →
3.0.7 15 Sep 2025 H1 non-standard No Details →
3.0.6 15 Sep 2025 C23 H57 M24 non-standard No Details →
3.0.5 11 Aug 2025 C4 H1 non-standard Yes Details →
3.0.4 11 Jul 2025 C25 H60 M24 non-standard No Details →
3.0.3 27 Jun 2025 C25 H60 M24 non-standard No Details →
3.0.2 11 Jun 2025 C25 H60 M24 non-standard No Details →
3.0.1 29 May 2025 H1 non-standard No Details →
3.0.0 15 May 2025 C25 H59 M24 non-standard No Details →
2.2.8 28 Apr 2025 C25 H59 M24 non-standard No Details →
2.2.7-patch.1 14 Mar 2025 C24 H59 M24 non-standard No Details →
2.2.7 06 Mar 2025 C25 H58 M24 non-standard No Details →
2.2.6-hotfix.1 28 Feb 2025 C25 H58 M24 non-standard No Details →
2.2.6 28 Feb 2025 C25 H58 M24 non-standard No Details →
2.2.5 04 Feb 2025 C25 H58 M24 non-standard No Details →
2.2.4 14 Jan 2025 C25 H58 M24 non-standard No Details →
2.2.3 23 Dec 2024 C25 H58 M24 non-standard No Details →
2.2.2 10 Dec 2024 C25 H58 M24 non-standard No Details →
2.2.1 29 Nov 2024 C25 H58 M24 non-standard No Details →
2.2.0 28 Nov 2024 C25 H58 M24 non-standard No Details →
2.1.5 19 Nov 2024 C25 H58 M24 non-standard No Details →
2.1.4 13 Nov 2024 C25 H58 M24 non-standard No Details →
2.1.3 23 Oct 2024 C26 H59 M24 non-standard No Details →
2.1.2 09 Oct 2024 C26 H59 M24 non-standard No Details →
2.1.1 18 Sep 2024 C26 H59 M24 non-standard No Details →
2.1.0 17 Sep 2024 C26 H59 M24 non-standard No Details →
2.0.7 28 Aug 2024 C26 H59 M24 non-standard No Details →
2.0.6 27 Aug 2024 C26 H59 M24 non-standard No Details →
2.0.5 12 Aug 2024 C26 H59 M24 non-standard No Details →
2.0.4 07 Aug 2024 C26 H59 M24 non-standard No Details →
2.0.3 07 Aug 2024 C26 H59 M24 non-standard No Details →
2.0.2 05 Aug 2024 C26 H59 M24 non-standard No Details →
2.0.1 23 Jul 2024 C26 H59 M24 non-standard No Details →
2.0.0 22 Jul 2024 C26 H59 M24 non-standard No Details →
1.8.4 15 Jul 2024 C26 H59 M24 non-standard No Details →
1.8.3 26 Jun 2024 C26 H59 M24 non-standard No Details →
1.8.2 11 Jun 2024 C26 H59 M24 non-standard No Details →
1.8.1 31 May 2024 C26 H59 M24 non-standard No Details →
1.8.0 21 May 2024 C26 H60 M24 non-standard No Details →
1.7.2 09 May 2024 C26 H60 M24 non-standard No Details →
1.7.1 06 May 2024 C26 H60 M24 non-standard No Details →
1.6.6 25 Apr 2024 C26 H60 M24 non-standard No Details →
1.6.5 12 Apr 2024 C26 H60 M24 non-standard No Details →
1.6.4 09 Apr 2024 C26 H60 M24 non-standard No Details →
1.6.3 04 Apr 2024 C26 H60 M24 non-standard No Details →
1.6.2 19 Mar 2024 C26 H60 M24 non-standard No Details →
1.6.1 12 Mar 2024 C26 H60 M24 non-standard No Details →
1.6.0 27 Feb 2024 C26 H60 M24 non-standard No Details →
1.5.1 20 Feb 2024 C26 H60 M24 non-standard No Details →
1.5.0 05 Feb 2024 C26 H60 M24 non-standard No Details →
1.4.12 31 Jan 2024 C26 H60 M24 non-standard No Details →
1.4.11 25 Jan 2024 C26 H60 M24 non-standard No Details →
1.4.10 16 Jan 2024 C26 H60 M24 non-standard No Details →
1.4.9 03 Jan 2024 C26 H60 M24 non-standard No Details →
1.4.8 30 Dec 2023 C26 H60 M24 non-standard No Details →
1.4.7 20 Dec 2023 C26 H60 M24 non-standard No Details →
1.4.6 18 Dec 2023 C26 H60 M24 non-standard No Details →
1.4.5 09 Dec 2023 C26 H60 M24 non-standard No Details →
1.4.4 08 Dec 2023 C26 H60 M24 non-standard No Details →
1.4.3 24 Nov 2023 C26 H60 M24 non-standard No Details →
1.4.2 10 Nov 2023 C26 H60 M24 non-standard No Details →
1.4.1 09 Nov 2023 C26 H60 M24 non-standard No Details →
1.4.0 09 Nov 2023 C26 H60 M24 non-standard No Details →
1.4.0-rc.1 07 Nov 2023 C26 H60 M24 non-standard No Details →
1.3.9 03 Nov 2023 C26 H60 M24 non-standard No Details →
1.3.8-rc.1 24 Oct 2023 C26 H60 M24 non-standard No Details →
1.3.8 12 Oct 2023 C26 H60 M24 non-standard No Details →
1.3.7 09 Oct 2023 C26 H60 M24 non-standard No Details →
1.3.6 21 Sep 2023 C26 H60 M24 non-standard No Details →
1.3.5 15 Sep 2023 C26 H60 M24 non-standard No Details →
1.3.4 23 Aug 2023 C26 H60 M24 non-standard No Details →
1.3.3 09 Aug 2023 C26 H60 M24 non-standard No Details →
1.3.2 30 Jul 2023 C26 H60 M24 non-standard No Details →
1.3.1 29 Jul 2023 C26 H60 M24 non-standard No Details →
1.3.0 28 Jul 2023 C26 H60 M24 non-standard No Details →
1.2.16 18 Jul 2023 C26 H60 M24 non-standard No Details →
1.2.15 12 Jul 2023 C26 H60 M24 non-standard No Details →
1.2.14 05 Jul 2023 C26 H60 M24 non-standard No Details →
1.2.13 22 Jun 2023 C26 H60 M24 non-standard No Details →
1.2.12 14 Jun 2023 C26 H60 M24 non-standard No Details →
1.2.11 09 Jun 2023 C26 H60 M24 non-standard No Details →
1.2.10 27 May 2023 C26 H60 M24 non-standard No Details →
1.2.9 27 May 2023 C26 H60 M24 non-standard No Details →
1.2.8 27 May 2023 C26 H60 M24 non-standard No Details →
1.2.7 26 May 2023 C26 H60 M24 non-standard No Details →
1.2.6 17 May 2023 C26 H60 M24 non-standard No Details →
1.2.5 11 May 2023 C26 H60 M24 non-standard No Details →
1.2.4 04 May 2023 C26 H60 M24 non-standard No Details →
1.2.3 28 Apr 2023 C26 H60 M24 non-standard No Details →
1.2.2 22 Apr 2023 C26 H60 M24 non-standard No Details →
1.2.1 20 Apr 2023 C26 H60 M24 non-standard No Details →
1.1.1 14 Apr 2023 C26 H60 M24 — No Details →
1.1.0 13 Apr 2023 C26 H60 M24 — No Details →
1.0.1 10 Apr 2023 C26 H60 M24 — No Details →
1.0.0 10 Apr 2023 C26 H60 M24 — No Details →

All 104 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 10
  • 2025 26
  • 2026 82

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 84 of the 118 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for flowise

The 5 most severe of 118 vulnerabilities recorded for this package

Search all 118 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Critical Remote Code Execution Vulnerability in Flowise Package 10.0 critical 3.0.6 15 Sep 2025
Critical Remote Code Execution Vulnerability in Flowise Package 10.0 critical No fix published 14 Mar 2025
CVE-2026-40933: Flowise Authenticated RCE via MCP Adapters 9.9 critical 3.1.0 16 Apr 2026
CVE-2025-61913: Flowise Arbitrary File Write Vulnerability 9.9 critical 3.0.8 09 Oct 2025
CVE-2025-55346: Flowise Vulnerable to Remote Code Execution via Dynamic Function Constructor Injection 9.8 critical No fix published 06 Oct 2025

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

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

Is flowise safe to use?

Vulert records 118 vulnerabilities for flowise in npm: 31 critical, 63 high, 24 medium and 0 low. 20 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is flowise's Vulert package health score?

Vulert scores flowise 35/100, which reads as risky. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of flowise affected?

Yes. 3.1.4, the version you would install today, has 20 known vulnerabilities, and 20 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of flowise should I use?

3.1.4 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does flowise have?

118 vulnerabilities are recorded for flowise in the npm ecosystem: 31 critical, 63 high, 24 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new flowise vulnerabilities disclosed?

84 vulnerabilities were recorded for flowise in the last 12 months, and the oldest entry in this database dates to 29 Apr 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of flowise are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.