CVE-2026-119192
7.5HighPublished 17 Nov 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.1-flash-lite
High
0CVSS v3.110
- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User action
- None
- Impact
- High impact on integrity
- Weakness
- CWE-347
What an attacker gets
Unauthenticated attackers can forge RSA signatures to bypass authentication or validation checks. This requires the target to use an RSA public key with a low exponent, such as e=3.
Root cause
The library uses a lenient BER parser that fails to enforce canonical DER encoding, allowing attackers to inject malicious data into the DigestInfo structure.
Affected versions
node-forge versions prior to 1.4.1
CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Fix & remediation
Upgrade node-forge to version 1.4.1 or later. If you cannot upgrade, ensure all RSA public keys in use have an exponent larger than 3.
$ npm install node-forge@1.4.1AI-suggested. Run it in staging first and check it against the vendor advisory. Why?
NVD description
Forge, also called node-forge, is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, publicKey.verify() with the default RSASSA-PKCS1-V1_5 scheme in lib/rsa.js parses the recovered DigestInfo with the lenient BER parser asn1.fromDer() and validates its structure with digestInfoValidator without requiring canonical DER bytes. Non-minimal or indefinite lengths, malformed parameter values, and non-canonical object identifier encodings with padded subidentifiers or trailing bytes can leave attacker-controlled data inside an accepted DigestInfo. When the verifying RSA public key uses a low exponent such as e=3, an attacker can use that encoding slack to forge a signature without the private key. The same path is used by X.509 certificate and PKCS#7 signature verification. This issue is fixed in version 1.4.1.