VulertSecurity VulertSecurity

Vulnerability Database · npm · node-forge · Version

node-forge 0.2.12

0.2.12 is affected by 16 vulnerabilities.

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 10 Medium 3 Low 3 Unrated 0

All node-forge versions & vulnerabilities → Search the database for this package →
Released 25 Sep 2013 Licence BSD-3-Clause OR GPL-2.0 Also known from other sources 0 Newer releases 134 Database updated 23/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 0.2.12 vulnerabilities

16 vulnerabilities cover node-forge 0.2.12. Scroll the table for all of them, or open the full list in the database.

Vulnerability Severity Fixed version Disclosed
CVE-2020-7720: Prototype Pollution in node-forge 8.8 high 0.10.0 14 Sep 2020
CVE-2025-66031: node-forge Uncontrolled Recursion Vulnerability Leading to Denial-of-Service 8.7 high 1.3.2 26 Nov 2025
CVE-2025-12816: node-forge ASN.1 Validator Desynchronization Vulnerability 8.6 high 1.3.2 26 Nov 2025
CVE-2026-85393: node-forge Vulnerability in RSA PKCS#1 v1.5 Signature Verification 7.5 high No fix published 03 Sep 2026
CVE-2026-33895: Node-Forge Ed25519 Signature Forgery Vulnerability 7.5 high 1.4.0 26 Mar 2026
CVE-2026-33894: Node-Forge RSA-PKCS Signature Forgery Vulnerability 7.5 high 1.4.0 26 Mar 2026
CVE-2026-33891: node-forge Denial of Service via Infinite Loop in BigInteger.modInverse() 7.5 high 1.4.0 26 Mar 2026
CVE-2022-24772: Improper Verification of Cryptographic Signature in node-forge 7.5 high 1.3.0 18 Mar 2022
CVE-2022-24771: Improper Verification of Cryptographic Signature in node-forge 7.5 high 1.3.0 18 Mar 2022
CVE-2026-33896: node-forge BasicConstraints Bypass in Certificate Chain Verification 7.4 high 1.4.0 26 Mar 2026
CVE-2025-66030: node-forge ASN.1 OID Integer Truncation Vulnerability 6.3 medium 1.3.2 26 Nov 2025
CVE-2022-0122: Open Redirect in node-forge 6.1 medium 1.0.0 21 Jan 2022
CVE-2022-24773: Improper Verification of Cryptographic Signature in node-forge 5.3 medium 1.3.0 18 Mar 2022
Prototype Pollution in node-forge debug API N/A low 1.0.0 08 Jan 2022
Prototype Pollution in node-forge util.setPath API N/A low 0.10.0 08 Jan 2022
URL parsing vulnerability in node-forge N/A low 1.0.0 08 Jan 2022

Looking for another version, or everything Vulert holds for node-forge?

All versions → Full vulnerability list →

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 0.2.12

Is node-forge 0.2.12 vulnerable?

Yes. 16 vulnerabilities in the Vulert database cover node-forge 0.2.12: 0 critical, 10 high, 3 medium and 3 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 0.2.12?

1.4.0 is the version Vulert recommends for this release line. The version table on the package page lists every release with the vulnerabilities recorded against it.

Is 0.2.12 the latest release of node-forge?

No. 0.2.12 was published 25 Sep 2013, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.

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.