Vulnerability Database · npm · node-forge · Version
node-forge 1.4.0
1.4.0 is affected by 1 vulnerability.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to. The upgrade Vulert recommends: 1.4.0.
Critical 0 High 1 Medium 0 Low 0 Unrated 0
-
Released 24 Mar 2026
Status latest release
Licence BSD-3-Clause OR GPL-2.0
Also known from other sources 1
Newer releases 134
Database updated 22/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
node-forge 1.4.0 vulnerabilities
1 vulnerability cover node-forge 1.4.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2026-85393: node-forge Vulnerability in RSA PKCS#1 v1.5 Signature Verification | 7.5 high | No fix published | 03 Sep 2026 |
Looking for another version, or everything Vulert holds for node-forge?
Questions
About node-forge 1.4.0
Is node-forge 1.4.0 vulnerable?
Yes. 1 vulnerability in the Vulert database cover node-forge 1.4.0: 0 critical, 1 high, 0 medium and 0 low. The upgrade Vulert recommends is 1.4.0, and each entry above names the fixed version to move to.
Which version of node-forge should I use instead of 1.4.0?
1.4.0 is the version Vulert recommends for this release line, which is also the release the publisher currently ships. The version table on the package page lists every release with the vulnerabilities recorded against it.
Is 1.4.0 the latest release of node-forge?
Yes. 1.4.0 is the current release, published 24 Mar 2026. Staying on the current line is what keeps you inside the publisher's fixes.
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.