node-forge · Forge: X.509 pathLenConstraint not enforced by verifyCertificateChain() for CA certificates without keyUsage
Affects node-forgeSource GCVE Database
Not known to be exploited · CVSS 5.9 Medium : 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 | 5.9 |
|---|
- Patch
- Available – fixed in 1.4.1
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/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
Upgrade node-forge to version 1.4.1 or later, where the pathLenConstraint is enforced regardless of the presence of the keyUsage extension. If upgrading is not immediately possible, applications can implement a custom verification callback to reject certificate chains where a CA certificate's pathLenConstraint is violated. Alternatively, re-issuing CA certificates to include a keyUsage extension with keyCertSign restores enforcement in affected versions.
Description
A vulnerability in node-forge's pki.verifyCertificateChain() function causes it to ignore the pathLenConstraint in CA certificates that lack a keyUsage extension. This allows certificate chains with more intermediate CAs than allowed by the pathLenConstraint to be accepted. The issue is fixed in node-forge 1.4.1.
References
- github.com/digitalbazaar/forge/security/advisories/GHSA-h46v-rmh6-fq4f (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-119189 (opens in a new tab)
- github.com/digitalbazaar/forge/commit/696db92348623e88cc63c35f0a89ede481d55ad0 (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)