Forge fails to enforce X.509 name constraints in chain validation
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Spoofing
- Confidentiality · integrity · availability
- High · High · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-295.
Summary
Forge (node-forge) before 1.4.3 does not enforce X.509 nameConstraints in pki.verifyCertificateChain(), an improper certificate validation flaw (CWE-295). A name-constrained certificate authority can issue a leaf certificate for names outside its permitted subtree, and Forge accepts the chain. An attacker who holds that authority's private key or can obtain an out-of-scope certificate can impersonate names outside the delegated namespace. A public exploit is linked in the references.
Written with Claude Haiku 5.5 from the sources below · 2026-11-16
Description from the CNA
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.3, pki.verifyCertificateChain() in lib/x509.js does not decode or enforce the X.509 nameConstraints extension while validating certificate paths. A name-constrained certificate authority with a non-critical extension can therefore issue a leaf certificate with a subjectAltName dNSName or subject commonName outside a permitted subtree or inside an excluded subtree, and node-forge accepts the chain. Exploitation requires a name-constrained CA that chains to a trusted root and either its private key or the ability to obtain an out-of-scope certificate, allowing impersonation of names outside the delegated namespace, including against forge.tls clients. Chains without nameConstraints are not affected, and affected versions safely reject critical nameConstraints as unsupported rather than accepting them. This issue is fixed in version 1.4.3.
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Total
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| digitalbazaar | forge | before 1.4.3 | 1.4.3 | Patch available | CNA |
- forge Vendordigitalbazaar Affected before 1.4.3 Fixed in 1.4.3 Patch available CNA
CPE configurations NVD · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:digitalbazaar:forge:*:*:*:*:*:node.js:*:* | before 1.4.3 | Vulnerable | digitalbazaar |
- cpe:2.3:a:digitalbazaar:forge:*:*:*:*:*:node.js:*:* Versions before 1.4.3 Vulnerable ·digitalbazaar
Remediation
Upgrade Forge to version 1.4.3, which fixes this flaw.
Written with Claude Haiku 5.5 from the sources below · 2026-11-16
- Fix · CNA forge (digitalbazaar) Fixed in 1.4.3
Timeline
- 2026-11-10 Threatist record created from CVE-2026-125336
- 2026-11-12 Priority changed: MEDIUM → LOW
- 2026-11-13 CISA SSVC decision points changed
References
Patch 3
More digitalbazaar Forge vulnerabilities
- TI-2026-26254 Forge has a basicConstraints bypass in its certificate chain verification (RFC 5280 violation) CVSS 3.1CRITICAL 9.1
- TI-2026-82739 Resource exhaustion in Forge ASN.1 parsing via nested BIT STRINGs CVSS 3.1HIGH 7.5
- TI-2026-82735 Recursive TLS record processing in Forge enables denial of service CVSS 3.1HIGH 7.5
- TI-2026-82733 Forge PKCS#12 input can bypass password integrity checks CVSS 3.1HIGH 7.5
- TI-2026-82730 Regular expression denial of service in Forge PEM decoding CVSS 3.1HIGH 7.5
- TI-2026-26253 Forge has signature forgery in Ed25519 due to missing S > L check CVSS 3.1HIGH 7.5
Sources
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences