VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

flowise-components: vulnerability history, versions and safety

flowise-components is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 110 releases, from Apr 2025 to Aug 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded C1 H2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 04 Aug 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all flowise-components vulnerabilities

Vulert verdict on flowise-components 3.1.4 i

Updated on 23 Oct 2026

Good news: 3.1.4, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 3.

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

What to do: Stay on 3.1.4 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.1.4 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.1.4 — unaffected i
  • Vulnerabilities on record 3 over 1 year · 2 in the last year i
  • Latest disclosure 04 Aug 2026 i
  • Highest CVSS 9.4 i
  • With no published fix 0 i
  • Depended on by 3 packages i
  • Last release 2 months ago i
  • Licence non-standard i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 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-components, 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 none non-standard — Details →
3.1.3 25 Jun 2026 none non-standard — Details →
3.1.2 14 Apr 2026 C1 H1 non-standard Yes Details →
3.1.1 23 Mar 2026 C1 H1 non-standard Yes Details →
3.1.0 16 Mar 2026 C1 H1 non-standard Yes Details →
3.0.13 03 Feb 2026 C1 H1 non-standard Yes Details →
3.0.12 05 Dec 2025 C1 H1 non-standard Yes Details →
3.0.11 16 Nov 2025 C1 H1 non-standard Yes Details →
3.0.10 06 Nov 2025 C1 H1 non-standard Yes Details →
3.0.9 06 Nov 2025 C1 H1 non-standard Yes Details →
3.0.8 08 Oct 2025 C1 H1 non-standard Yes Details →
3.0.7 15 Sep 2025 C1 H1 non-standard Yes Details →
3.0.6 15 Sep 2025 C1 H1 non-standard Yes Details →
3.0.5 11 Aug 2025 C1 H1 non-standard Yes Details →
3.0.4 11 Jul 2025 C1 H1 non-standard Yes Details →
3.0.3 27 Jun 2025 C1 H1 non-standard Yes Details →
3.0.2 11 Jun 2025 C1 H1 non-standard Yes Details →
3.0.1 29 May 2025 C1 H1 non-standard Yes Details →
3.0.0 15 May 2025 C1 H1 non-standard Yes Details →
2.2.8 28 Apr 2025 C1 H1 non-standard Yes Details →
2.2.7-patch.1 07 Mar 2025 C1 H1 non-standard Yes Details →
2.2.7 06 Mar 2025 C1 H1 non-standard Yes Details →
2.2.6 28 Feb 2025 C1 H1 non-standard Yes Details →
2.2.5 04 Feb 2025 C1 H1 non-standard Yes Details →
2.2.4 14 Jan 2025 C1 H1 non-standard Yes Details →
2.2.3 23 Dec 2024 C1 H2 non-standard Yes Details →
2.2.2 10 Dec 2024 C1 H2 non-standard Yes Details →
2.2.1 29 Nov 2024 C1 H2 non-standard Yes Details →
2.2.0 28 Nov 2024 C1 H2 non-standard Yes Details →
2.1.5 19 Nov 2024 C1 H2 non-standard Yes Details →
2.1.4 13 Nov 2024 C1 H2 non-standard Yes Details →
2.1.3 23 Oct 2024 C1 H2 non-standard Yes Details →
2.1.2 09 Oct 2024 C1 H2 non-standard Yes Details →
2.1.1 17 Sep 2024 C1 H2 non-standard Yes Details →
2.1.0 17 Sep 2024 C1 H2 non-standard Yes Details →
2.0.7 28 Aug 2024 C1 H2 non-standard Yes Details →
2.0.6 27 Aug 2024 C1 H2 non-standard Yes Details →
2.0.5 12 Aug 2024 C1 H2 non-standard Yes Details →
2.0.4 07 Aug 2024 C1 H2 non-standard Yes Details →
2.0.3 07 Aug 2024 C1 H2 non-standard Yes Details →
2.0.2 05 Aug 2024 C1 H2 non-standard Yes Details →
2.0.1 23 Jul 2024 C1 H2 non-standard Yes Details →
2.0.0 22 Jul 2024 C1 H2 non-standard Yes Details →
1.8.6 15 Jul 2024 C1 H2 non-standard Yes Details →
1.8.5 26 Jun 2024 C1 H2 non-standard Yes Details →
1.8.4 26 Jun 2024 C1 H2 non-standard Yes Details →
1.8.3 11 Jun 2024 C1 H2 non-standard Yes Details →
1.8.2 03 Jun 2024 C1 H2 non-standard Yes Details →
1.8.1 31 May 2024 C1 H2 non-standard Yes Details →
1.8.0 21 May 2024 C1 H2 non-standard Yes Details →
1.7.2 09 May 2024 C1 H2 non-standard Yes Details →
1.7.1 06 May 2024 C1 H2 non-standard Yes Details →
1.7.0 06 May 2024 C1 H2 non-standard Yes Details →
1.6.10 29 Apr 2024 C1 H2 non-standard Yes Details →
1.6.9 26 Apr 2024 C1 H2 non-standard Yes Details →
1.6.8 25 Apr 2024 C1 H2 non-standard Yes Details →
1.6.7 12 Apr 2024 C1 H2 non-standard Yes Details →
1.6.6 09 Apr 2024 C1 H2 non-standard Yes Details →
1.6.5 04 Apr 2024 C1 H2 non-standard Yes Details →
1.6.4 19 Mar 2024 C1 H2 non-standard Yes Details →
1.6.3 12 Mar 2024 C1 H2 non-standard Yes Details →
1.6.2 27 Feb 2024 C1 H2 non-standard Yes Details →
1.6.1 20 Feb 2024 C1 H2 non-standard Yes Details →
1.6.0 05 Feb 2024 C1 H2 non-standard Yes Details →
1.5.3 31 Jan 2024 C1 H2 non-standard Yes Details →
1.5.2 25 Jan 2024 C1 H2 non-standard Yes Details →
1.5.1 16 Jan 2024 C1 H2 non-standard Yes Details →
1.5.0 30 Dec 2023 C1 H2 non-standard Yes Details →
1.4.9 20 Dec 2023 C1 H2 non-standard Yes Details →
1.4.8 19 Dec 2023 C1 H2 non-standard Yes Details →
1.4.7 18 Dec 2023 C1 H2 non-standard Yes Details →
1.4.6 08 Dec 2023 C1 H2 non-standard Yes Details →
1.4.5 29 Nov 2023 C1 H2 non-standard Yes Details →
1.4.4 27 Nov 2023 C1 H2 non-standard Yes Details →
1.4.3 24 Nov 2023 C1 H2 non-standard Yes Details →
1.4.2 10 Nov 2023 C1 H2 non-standard Yes Details →
1.4.1 09 Nov 2023 C1 H2 non-standard Yes Details →
1.4.0 09 Nov 2023 C1 H2 non-standard Yes Details →
1.4.0-rc.1 07 Nov 2023 C1 H2 non-standard Yes Details →
1.3.11 03 Nov 2023 C1 H2 non-standard Yes Details →
1.3.10 12 Oct 2023 C1 H2 non-standard Yes Details →
1.3.9 12 Oct 2023 C1 H2 non-standard Yes Details →
1.3.8 09 Oct 2023 C1 H2 non-standard Yes Details →
1.3.7 21 Sep 2023 C1 H2 non-standard Yes Details →
1.3.6 20 Sep 2023 C1 H2 non-standard Yes Details →
1.3.5-alpha.0 20 Sep 2023 C1 H2 non-standard Yes Details →
1.3.5 15 Sep 2023 C1 H2 non-standard Yes Details →
1.3.4 23 Aug 2023 C1 H2 non-standard Yes Details →
1.3.3 09 Aug 2023 C1 H2 non-standard Yes Details →
1.3.2 30 Jul 2023 C1 H2 non-standard Yes Details →
1.3.1 29 Jul 2023 C1 H2 non-standard Yes Details →
1.3.0 28 Jul 2023 C1 H2 non-standard Yes Details →
1.2.17 18 Jul 2023 C1 H2 non-standard Yes Details →
1.2.16 12 Jul 2023 C1 H2 non-standard Yes Details →
1.2.15 05 Jul 2023 C1 H2 non-standard Yes Details →
1.2.14 22 Jun 2023 C1 H2 non-standard Yes Details →
1.2.13 14 Jun 2023 C1 H2 non-standard Yes Details →
1.2.12 09 Jun 2023 C1 H2 non-standard Yes Details →
1.2.11 27 May 2023 C1 H2 non-standard Yes Details →
1.2.10 27 May 2023 C1 H2 non-standard Yes Details →
1.2.9 27 May 2023 C1 H2 — Yes Details →
1.2.8 26 May 2023 C1 H2 — Yes Details →
1.2.7 17 May 2023 C1 H2 — Yes Details →
1.2.6 11 May 2023 C1 H2 — Yes Details →
1.2.5 04 May 2023 C1 H2 — Yes Details →
1.2.4 28 Apr 2023 C1 H2 — Yes Details →
1.2.3 23 Apr 2023 C1 H2 — Yes Details →
1.2.2 22 Apr 2023 C1 H2 — Yes Details →
1.2.1 20 Apr 2023 C1 H2 — Yes Details →
1.1.1 13 Apr 2023 C1 H2 — Yes Details →
1.1.0 13 Apr 2023 C1 H2 — Yes Details →
1.0.0 10 Apr 2023 C1 H2 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for flowise-components

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-69256: Remote Code Execution Vulnerability in flowise-components and flowise 9.4 critical 3.1.3 04 Aug 2026
CVE-2025-29189: Flowise Components SQL Injection Vulnerability via tableName Parameter 7.6 high 2.2.4 09 Apr 2025
Arbitrary File Write Vulnerability in Flowise Packages 7.2 high 3.1.3 04 Aug 2026

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-components

Is flowise-components safe to use?

Vulert records 3 vulnerabilities for flowise-components in npm: 1 critical, 2 high, 0 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is flowise-components's Vulert package health score?

Vulert scores flowise-components 72/100, which reads as in good shape. 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).

Is the latest version of flowise-components affected?

No. 3.1.4, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of flowise-components 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-components have?

3 vulnerabilities are recorded for flowise-components in the npm ecosystem: 1 critical, 2 high, 0 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-components vulnerabilities disclosed?

2 vulnerabilities were recorded for flowise-components in the last 12 months, and the oldest entry in this database dates to 09 Apr 2025. 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-components 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-components for upcoming vulnerabilities?

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