node-forge signature verification bypass in certificate validation
digitalbazaar forge
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| node-forge npm |
|
|
Original description
Forge (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.
From the CVE record · GitHub_M
References
- github.com/digitalbazaar/forge/security/advisories/GHSA-9wg5-mj3p-v49qVendor advisory
- github.com/digitalbazaar/forge/commit/c7f42614d5166a77ddf11ce174b2601b14f6956bPatch
- github.com/digitalbazaar/forge/releases/tag/v1.4.1Release notes
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/118xxx/CVE-2026-118774.json
- nvd.nist.gov/vuln/detail/CVE-2026-118774
- github.com/digitalbazaar/forge