Vulnerability 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.
CVSS Score
LOW
Related Weaknesses (CWE)
References
- https://github.com/digitalbazaar/forge/commit/c7f42614d5166a77ddf11ce174b2601b14
- https://github.com/digitalbazaar/forge/releases/tag/v1.4.1
- https://github.com/digitalbazaar/forge/security/advisories/GHSA-9wg5-mj3p-v49q
FAQ
What is CVE-2026-118774?
CVE-2026-118774 is a vulnerability with a CVSS score of 3.7 (LOW). 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...
How severe is CVE-2026-118774?
CVE-2026-118774 has been rated LOW with a CVSS base score of 3.7/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-118774?
Check the references section above for vendor advisories and patch information. Review vendor security bulletins for remediation guidance.