Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to…
Historical advisory recorded 10 Nov 2026 16:25:21 UTC. Read the latest advisory.
nvd · CVE-2026-118774
PublishedForge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, the affected implementation used certificate.verify(child), _verifySignature(), lib/x509.js to process the relevant input or security decision. node-forge selected RSA padding and RSASSA-PSS parameters from the issuer certificate rather than the child certificate being verified. A child labeled as RSASSA-PSS could therefore be accepted with a PKCS#1 v1.5 signature when the issuer used PKCS#1 v1.5. The signature still had to be produced with the trusted issuer's private key, so this did not permit certificate identity forgery, but it could bypass policies that require a declared signature scheme. This issue is fixed in version 1.4.1.
Read the publisher's advisoryAffected versions, risk and source history
nvd · CVE-2026-118774
PublishedNVD analysis and CPE criteria are source context, not proof that a package or your environment is affected. Complete affected data, logical configurations and SSVC are retained in the original JSON.
Source analysis status: Analyzed
Weakness classifications: CWE-347
Original publisher date fields
published: 2026-10-29T19:17:19.863
lastModified: 2026-11-04T14:57:16.280
1 source CPE criteria · context only
- cpe:2.3:a:digitalbazaar:forge:*:*:*:*:*:*:*:*
The original JSON retains the logical configuration operators, exclusions and version bounds.
No normalized affected-package data is projected for this source revision. The original publisher record may contain additional product and version evidence; this does not establish that a package is unaffected.
Original source record · Cite this exact observation · Complete original publisher JSON