node-forge · Forge: verifyCertificateChain() removes trusted CA certificates with the same subject from the CA store
Affects node-forgeSource GCVE Database
Not known to be exploited · CVSS 3.7 Low : upgrade to 1.4.1 when convenient.
Data as of 31 Oct 2026, 01:55 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:N/A:LExploitation 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 30 Oct 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
A fix is available in node-forge version 1.4.1, which prevents modification of the CA store during verification. Users should upgrade to node-forge 1.4.1 or later. As a workaround, applications can pass a fresh CA store to each pki.verifyCertificateChain() call or ensure getIssuer() returns a copy of the candidate list to avoid modifying the original store. Passing the CA certificates as an array instead of a store object to forge.tls.createConnection() also mitigates the issue by creating a new store per connection.
Description
A vulnerability in node-forge versions prior to 1.4.1 causes the CA store to lose trusted CA certificates with duplicate subject names during certificate chain verification. When verifying a chain, the function removes certificates from the CA store's internal list, leading to persistent denial of service for subsequent verifications involving those certificates. This affects applications that reuse a CA store containing multiple certificates sharing the same subject name. The issue is fixed in node-forge 1.4.1.
References
- github.com/digitalbazaar/forge/security/advisories/GHSA-4487-j8r4-4g2f (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-118780 (opens in a new tab)
- github.com/digitalbazaar/forge/commit/f6555609bd30f442fbfacd543155928ceccf98d0 (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)