Vulnerability Database · npm · Package report

node-forge: vulnerability history, versions and safety

node-forge is a package in the npm ecosystem. Vulert records 16 vulnerabilities for it across 120 releases, from Sep 2020 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
16 vulnerabilities recorded H10 M3 L3
i
1 with no fix published

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

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

Most recent disclosure 03 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on node-forge 1.4.0 i

Updated on 22 Oct 2026

Careful: 1.4.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

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 1.4.0 — affected i
  • Vulnerabilities on record 16 over 5 years · 8 in the last year i
  • Latest disclosure 03 Sep 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 1 i
  • Depended on by 64,969 packages i
  • Stars 5,342 i
  • OpenSSF scorecard 3/10 i
  • Last release 6 months ago i
  • Licence BSD-3-Clause OR GPL-2.0 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 node-forge, 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
1.4.0 24 Mar 2026 H1 BSD-3-Clause OR GPL-2.0 No Details →
1.3.3 02 Dec 2025 H5 BSD-3-Clause OR GPL-2.0 No Details →
1.3.2 25 Nov 2025 H5 BSD-3-Clause OR GPL-2.0 No Details →
1.3.1 30 Mar 2022 H7 M1 BSD-3-Clause OR GPL-2.0 No Details →
1.3.0 17 Mar 2022 H7 M1 BSD-3-Clause OR GPL-2.0 No Details →
1.2.1 11 Jan 2022 H9 M2 BSD-3-Clause OR GPL-2.0 No Details →
1.2.0 08 Jan 2022 H9 M2 BSD-3-Clause OR GPL-2.0 No Details →
1.1.0 07 Jan 2022 H9 M2 BSD-3-Clause OR GPL-2.0 No Details →
1.0.0 05 Jan 2022 H9 M2 BSD-3-Clause OR GPL-2.0 No Details →
0.10.0 02 Sep 2020 H9 M3 L2 BSD-3-Clause OR GPL-2.0 No Details →
0.9.2 02 Sep 2020 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.9.1 26 Sep 2019 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.9.0 05 Sep 2019 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.8.5 19 Jun 2019 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.8.4 22 May 2019 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.8.3 15 May 2019 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.8.2 18 Mar 2019 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.8.1 23 Feb 2019 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.8.0 01 Feb 2019 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.7.6 14 Aug 2018 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.7.5 31 Mar 2018 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.7.4 07 Mar 2018 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.7.3 05 Mar 2018 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.7.2 27 Feb 2018 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.7.1 27 Mar 2017 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.7.0 07 Feb 2017 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.49 07 Feb 2017 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.48 25 Jan 2017 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.47 14 Jan 2017 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.46 07 Dec 2016 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.45 29 Oct 2016 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.44 18 Oct 2016 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.43 07 Oct 2016 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.42 04 Aug 2016 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.41 15 Jul 2016 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.40 28 Jun 2016 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.39 12 Feb 2016 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.38 10 Nov 2015 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.37 23 Oct 2015 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.35 26 Sep 2015 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.34 30 Jun 2015 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.33 26 Jun 2015 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.32 25 Jun 2015 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.31 24 Jun 2015 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.30 27 May 2015 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.29 20 May 2015 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.28 19 May 2015 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.27 18 May 2015 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.26 23 Apr 2015 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.25 16 Apr 2015 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.24 15 Apr 2015 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.23 08 Apr 2015 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.22 02 Apr 2015 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.21 09 Mar 2015 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.20 01 Dec 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.19 01 Dec 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.18 12 Nov 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.16 24 Oct 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.14 26 Sep 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.13 26 Sep 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.12 21 Jul 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.11 08 Jul 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.10 07 Jul 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.9 03 Jul 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.8 23 Jun 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.7 16 Jun 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.6 12 Jun 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.5 11 Jun 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.4 10 Jun 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.3 10 Jun 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.2 09 Jun 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.1 09 Jun 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.6.0 09 Jun 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.5.5 27 May 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.5.4 26 May 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.5.3 21 May 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.5.2 21 May 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.5.1 21 May 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.4.3 16 May 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.4.2 16 May 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.4.1 16 May 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.4.1-dev 16 May 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.3.0 13 May 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.37 12 Apr 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.36 03 Apr 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.35 27 Mar 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.34 21 Mar 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.33 20 Mar 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.32 19 Mar 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.31 10 Mar 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.30 16 Feb 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.29 05 Feb 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.28 29 Jan 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.27 22 Jan 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.26 15 Jan 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.25 15 Jan 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.24 15 Jan 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.23 08 Jan 2014 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.22 11 Dec 2013 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.21 02 Dec 2013 H10 M3 L3 BSD-3-Clause OR GPL-2.0 No Details →
0.2.20 30 Nov 2013 H10 M3 L3 — No Details →
0.2.19 27 Nov 2013 H10 M3 L3 — No Details →
0.2.18 15 Nov 2013 H10 M3 L3 — No Details →
0.2.17 23 Oct 2013 H10 M3 L3 — No Details →
0.2.15 16 Oct 2013 H10 M3 L3 — No Details →
0.2.14 28 Sep 2013 H10 M3 L3 — No Details →
0.2.13 28 Sep 2013 H10 M3 L3 — No Details →
0.2.12 25 Sep 2013 H10 M3 L3 — No Details →
0.2.11 20 Sep 2013 H10 M3 L3 — No Details →
0.2.10 19 Sep 2013 H10 M3 L3 — No Details →
0.2.9 19 Sep 2013 H10 M3 L3 — No Details →
0.2.8 19 Sep 2013 H10 M3 L3 — No Details →
0.2.7 18 Sep 2013 H10 M3 L3 — No Details →
0.2.6 15 Sep 2013 H10 M3 L3 — No Details →
0.2.5 13 Sep 2013 H10 M3 L3 — No Details →
0.2.4 19 Aug 2013 H10 M3 L3 — No Details →
0.2.3 17 Aug 2013 H10 M3 L3 — No Details →
0.2.2 16 Aug 2013 H10 M3 L3 — No Details →
0.2.1 15 Aug 2013 H10 M3 L3 — No Details →
0.2.0 14 Aug 2013 H10 M3 L3 — No Details →

The newest 120 of 134 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2020 1
  • 2022 7
  • 2025 3
  • 2026 5

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

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 node-forge

Is node-forge safe to use?

Vulert records 16 vulnerabilities for node-forge in npm: 0 critical, 10 high, 3 medium and 3 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is node-forge's Vulert package health score?

Vulert scores node-forge 60/100, which reads as usable, but worth attention. 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 node-forge affected?

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

Which version of node-forge should I use?

1.4.0 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 node-forge have?

16 vulnerabilities are recorded for node-forge in the npm ecosystem: 0 critical, 10 high, 3 medium and 3 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new node-forge vulnerabilities disclosed?

8 vulnerabilities were recorded for node-forge in the last 12 months, and the oldest entry in this database dates to 14 Sep 2020. 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 node-forge 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 node-forge for upcoming vulnerabilities?

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