node-forge certificate validation bypass via deprecated extension OIDs
digitalbazaar forge
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| node-forge npm |
|
|
Original description
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, node-forge parsed deprecated extension OIDs 2.5.29.10 and 2.5.29.13 as basicConstraints, and pki.verifyCertificateChain() used the first extension with that name. Exploitation requires a CA trusted by the application to issue a certificate carrying an attacker-supplied deprecated-OID extension, commonly because the CA copies extensions from a certificate signing request. By placing a permissive deprecated extension before the genuine 2.5.29.19 basicConstraints extension, the certificate holder could have the certificate accepted as a CA and issue certificates for arbitrary names, enabling server or client impersonation. If the issuing CA adds a keyUsage extension without keyCertSign, node-forge rejects the chain. This issue is fixed in version 1.4.1.
From the CVE record · GitHub_M
References
- github.com/digitalbazaar/forge/security/advisories/GHSA-5x38-2vff-x55pVendor advisory
- github.com/digitalbazaar/forge/commit/58c06bc251856b409c30ecb35a93f5f6c9bbc84aPatch
- github.com/digitalbazaar/forge/releases/tag/v1.4.1Release notes
- github.com/CVEProject/cvelistV5/tree/main/cves/2026/119xxx/CVE-2026-119190.json
- nvd.nist.gov/vuln/detail/CVE-2026-119190
- github.com/digitalbazaar/forge