CVE-2026-118774: Forge · Certificate signature verified with the issuer's RSA signature scheme
Affects node-forgeSource GCVE Database
Not known to be exploited · CVSS 3.7 Low : upgrade to 1.4.1 when convenient.
Data as of 10 Nov 2026, 17:36 UTC
Thin evidence
One scorer or none| CNA (GitHub_M) | CVSS 3.1 | 3.7 |
|---|
- Patch
- Available – fixed in 1.4.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 10 Nov 2026.
What to do
Upgrade node-forge to 1.4.1.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| npmnode-forge | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
This vulnerability is fixed in node-forge version 1.4.1. Users should upgrade to node-forge 1.4.1 or later. As a workaround, applications that make decisions based on a certificate's signature algorithm can manually verify the signature using the certificate's declared algorithm and the issuer's public key.
Description
A vulnerability in node-forge prior to version 1.4.1 causes certificate signature verification to use the issuer certificate's RSA signature scheme instead of the certificate's own declared signature algorithm. This allows a certificate labeled as signed with RSASSA-PSS to be accepted if the issuer used PKCS#1 v1.5, despite the signature actually being PKCS#1 v1.5. The flaw does not allow forging certificates but can cause incorrect acceptance or rejection of certificate chains. The issue is fixed in node-forge 1.4.1.
References
- github.com/digitalbazaar/forge/security/advisories/GHSA-9wg5-mj3p-v49q (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-118774 (opens in a new tab)
- github.com/digitalbazaar/forge/commit/c7f42614d5166a77ddf11ce174b2601b14f6956b (opens in a new tab)
- github.com/digitalbazaar/forge (opens in a new tab)
- github.com/digitalbazaar/forge/releases/tag/v1.4.1 (opens in a new tab)