CVE-2026-118774
Forge (also called node-forge) is a native implementation of …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- github.com/digitalbazaar/forge/commit/c7f42614d5166a77ddf11ce174b2601b14f6956b
- github.com/digitalbazaar/forge/releases/tag/v1.4.1
- github.com/digitalbazaar/forge/security/advisories/GHSA-9wg5-mj3p-v49q
- nvd.nist.gov/vuln/detail/CVE-2026-118774
- github.com/advisories/GHSA-9wg5-mj3p-v49q
- nvd.nist.gov/vuln/detail/CVE-2026-118774
- cve.org/CVERecord?id=CVE-2026-118774
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.