VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

formidable: vulnerability history, versions and safety

formidable is a package in the npm ecosystem. Vulert records 2 vulnerabilities for it across 82 releases, from May 2022 to Apr 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
2 vulnerabilities recorded C1 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all formidable vulnerabilities

Vulert verdict on formidable 3.5.4 i

Updated on 23 Oct 2026

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

Package health score 76/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Key ecosystem project
  • Community Moderate

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

  • Current release 3.5.4 — unaffected i
  • Vulnerabilities on record 2 over 2 years · 0 in the last year i
  • Latest disclosure 26 Apr 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 3,353 packages i
  • Stars 7,176 i
  • OpenSSF scorecard 4/10 i
  • Last release 18 months ago i
  • Licence MIT 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 formidable, 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
4.0.0-rc.6 12 May 2025 none MIT — Details →
4.0.0-rc.5 30 Apr 2025 none MIT — Details →
4.0.0-rc.4 30 Apr 2025 none MIT — Details →
4.0.0-rc.3 30 Apr 2025 none MIT — Details →
4.0.0-rc.2 30 Apr 2025 none MIT — Details →
4.0.0-rc.1 30 Apr 2025 none MIT — Details →
2.1.5 30 Apr 2025 C1 MIT Yes Details →
2.1.4 23 Apr 2025 C1 MIT Yes Details →
3.5.4 23 Apr 2025 none MIT — Details →
2.1.3 19 Apr 2025 C1 MIT Yes Details →
3.5.3 18 Apr 2025 none MIT — Details →
3.5.2 18 Oct 2024 L1 MIT Yes Details →
3.5.1 25 Aug 2023 L1 MIT Yes Details →
3.5.0 28 Jun 2023 L1 MIT Yes Details →
3.4.0 17 Jun 2023 L1 MIT Yes Details →
3.3.2 16 Jun 2023 L1 MIT Yes Details →
2.1.2 01 Dec 2022 C1 MIT Yes Details →
2.1.1 01 Dec 2022 C1 MIT Yes Details →
2.1.0 01 Dec 2022 C1 MIT Yes Details →
3.2.5 04 Oct 2022 L1 MIT Yes Details →
3.2.4 19 May 2022 L1 MIT Yes Details →
3.2.3 26 Apr 2022 C1 L1 MIT Yes Details →
3.2.1 12 Dec 2021 C1 L1 MIT Yes Details →
3.2.0 09 Dec 2021 C1 L1 MIT Yes Details →
3.1.5 06 Dec 2021 C1 L1 MIT Yes Details →
3.1.4 30 Nov 2021 C1 L1 MIT Yes Details →
1.2.6 30 Oct 2021 C1 MIT Yes Details →
1.2.5 30 Oct 2021 C1 MIT Yes Details →
2.0.1 30 Oct 2021 C1 MIT Yes Details →
3.1.3 30 Oct 2021 C1 L1 MIT Yes Details →
3.1.2-canary.20211030 30 Oct 2021 C1 L1 MIT Yes Details →
2.0.0 30 Oct 2021 C1 MIT Yes Details →
1.2.4 30 Oct 2021 C1 MIT Yes Details →
1.2.3 30 Oct 2021 C1 MIT Yes Details →
3.1.1-canary.20211030 30 Oct 2021 C1 L1 MIT Yes Details →
2.0.0-canary.20210330 30 Oct 2021 C1 MIT Yes Details →
2.0.0-canary.20200504.1 04 May 2020 C1 MIT Yes Details →
2.0.0-canary.20200402.2 02 Apr 2020 C1 MIT Yes Details →
2.0.0-canary.20200402.1 02 Apr 2020 C1 MIT Yes Details →
2.0.0-canary.20200226.1 26 Feb 2020 C1 MIT Yes Details →
1.2.2 25 Feb 2020 C1 MIT Yes Details →
2.0.0-canary.20200212.1 12 Feb 2020 C1 MIT Yes Details →
2.0.0-dev.20200131.2 31 Jan 2020 C1 MIT Yes Details →
2.0.0-canary.20200131.1 31 Jan 2020 C1 MIT Yes Details →
2.0.0-dev.20200130.1 30 Jan 2020 C1 MIT Yes Details →
2.0.0-canary.20200129.32 29 Jan 2020 C1 MIT Yes Details →
2.0.0-canary.20200129.10 29 Jan 2020 C1 MIT Yes Details →
2.0.0-canary.20200129.5 29 Jan 2020 C1 MIT Yes Details →
2.0.0-canary.20200129.4 29 Jan 2020 C1 MIT Yes Details →
2.0.0-canary.20200129.3 29 Jan 2020 C1 MIT Yes Details →
2.0.0-canary.20200129.2 29 Jan 2020 C1 MIT Yes Details →
1.2.1 20 Mar 2018 C1 MIT Yes Details →
1.2.0 07 Mar 2018 C1 MIT Yes Details →
1.1.1 15 Jan 2017 C1 MIT Yes Details →
1.0.17 12 Feb 2015 C1 MIT Yes Details →
1.0.16 18 Dec 2014 C1 MIT Yes Details →
1.0.15 17 Jun 2014 C1 MIT Yes Details →
1.0.14 02 May 2013 C1 MIT Yes Details →
1.0.13 16 Mar 2013 C1 MIT Yes Details →
1.0.12 21 Feb 2013 C1 MIT Yes Details →
1.0.11 04 Jun 2012 C1 MIT Yes Details →
1.0.10 03 Jun 2012 C1 MIT Yes Details →
1.0.9 08 Mar 2012 C1 MIT Yes Details →
1.0.8 29 Nov 2011 C1 MIT Yes Details →
1.0.7 04 Nov 2011 C1 MIT Yes Details →
1.0.6 21 Sep 2011 C1 MIT Yes Details →
1.0.5 16 Sep 2011 C1 MIT Yes Details →
1.0.4 15 Sep 2011 C1 MIT Yes Details →
1.0.3 10 Sep 2011 C1 MIT Yes Details →
1.0.2 23 May 2011 C1 MIT Yes Details →
1.0.1 27 Apr 2011 C1 MIT Yes Details →
1.0.0 13 Apr 2011 C1 MIT Yes Details →
0.3.0 18 Jan 2011 C1 MIT Yes Details →
0.4.0 18 Jan 2011 C1 MIT Yes Details →
0.5.0 18 Jan 2011 C1 MIT Yes Details →
0.6.0 18 Jan 2011 C1 MIT Yes Details →
0.7.0 18 Jan 2011 C1 MIT Yes Details →
0.8.0 18 Jan 2011 C1 MIT Yes Details →
0.9.0 18 Jan 2011 C1 MIT Yes Details →
0.9.1 18 Jan 2011 C1 MIT Yes Details →
0.9.10 18 Jan 2011 C1 MIT Yes Details →
0.9.11 18 Jan 2011 C1 MIT Yes Details →
0.9.2 18 Jan 2011 C1 MIT Yes Details →
0.9.3 18 Jan 2011 C1 MIT Yes Details →
0.9.4 18 Jan 2011 C1 MIT Yes Details →
0.9.5 18 Jan 2011 C1 MIT Yes Details →
0.9.6 18 Jan 2011 C1 MIT Yes Details →
0.9.7 18 Jan 2011 C1 MIT Yes Details →
0.9.8 18 Jan 2011 C1 MIT Yes Details →
0.9.9 18 Jan 2011 C1 MIT Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for formidable

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Arbitrary File Upload Vulnerability in Formidable 9.8 critical 3.2.4 17 May 2022
CVE-2025-46653: Formidable Package Filename Guessing Vulnerability 3.1 low 3.5.3 26 Apr 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 formidable

Is formidable safe to use?

Vulert records 2 vulnerabilities for formidable in npm: 1 critical, 0 high, 0 medium and 1 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 formidable's Vulert package health score?

Vulert scores formidable 76/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 formidable affected?

No. 3.5.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 formidable should I use?

3.5.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 formidable have?

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

How often are new formidable vulnerabilities disclosed?

0 vulnerabilities were recorded for formidable in the last 12 months, and the oldest entry in this database dates to 17 May 2022. 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 formidable 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 formidable for upcoming vulnerabilities?

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