Improper Verification of Cryptographic Signature Affecting node-forge package, versions <1.4.1
Threat Intelligence
Snyk has a proof-of-concept or detailed explanation of how to exploit this vulnerability.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JS-NODEFORGE-22409019
- published11 Nov 2026
- disclosed10 Nov 2026
- creditOren Yomtov, Bronson Yen, Kamil Hałajda, pzartech, antonlissone, Brechard
Introduced: 10 Nov 2026
NewCVE-2026-119192 (opens in a new tab)How to fix?
Upgrade node-forge to version 1.4.1 or higher.
Overview
node-forge is a JavaScript implementations of network transports, cryptography, ciphers, PKI, message digests, and various utilities.
Affected versions of this package are vulnerable to Improper Verification of Cryptographic Signature in the key.verify() method in lib/rsa.js, which X.509 certificate and PKCS#7 verification also use. An attacker can make verification of an RSA PKCS#1 v1.5 signature succeed for an arbitrary message without the private key by adding extra elements to the nested DigestAlgorithm SEQUENCE of the DigestInfo, which the parser does not reject. Only verification with an RSA public key that has a low exponent such as e=3 is practically exploitable.
Workaround
This vulnerability can be avoided by not using RSA keys with a low public exponent (e=3) for signature verification.
Note: This is a bypass of the fix for the vulnerability described in CVE-2026-33894.