CVE-2026-118774: Forge: Certificate signature verified with the issuer's RSA signature scheme

November 10, 2026

When verifying a certificate, node-forge chose the RSA padding scheme (PKCS#1 v1.5 or RSASSA-PSS) and PSS parameters from the issuer certificate’s own signature algorithm instead of the certificate being verified. A certificate labeled as signed with RSASSA-PSS could pass verifyCertificateChain() with a PKCS#1 v1.5 signature. Fixed in node-forge 1.4.1.

References

github.com/advisories/GHSA-9wg5-mj3p-v49q
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

Code Behaviors & Features

Detect and mitigate CVE-2026-118774 with GitLab Dependency Scanning

Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Dependency Scanning using SBOM also detects vulnerabilities from proprietary advisories that this site does not include. Learn more about Dependency Scanning using SBOM →