Live › vulnerability › CVE-2026-119189
node-forge, a JavaScript TLS and crypto library, skips the pathLenConstraint check on CA certificates that lack a keyUsage extension. An attacker holding such a CA's private key or a subordinate CA certificate from it can build a chain longer than allowed that still passes pki.verifyCertificateChain().
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-29 20:26 UTC. All times on this page are UTC.
Applications that use node-forge to verify X.509 certificate chains, especially private PKIs whose CA certificates omit keyUsage. Public web PKI CA certificates normally include keyUsage, so they are less likely to be affected. Exploitation needs control of a constrained CA's private key or a subordinate CA certificate from it.
No product ranges from the sources yet.
npm ls node-forge.node-forge in package-lock.json, yarn.lock or pnpm-lock.yaml.pki.verifyCertificateChain() against private CAs that have pathLenConstraint and no keyUsage.1.4.1Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Forge (also called node-forge) is a native implementation of Transport Layer Security in JavaScript. Prior to 1.4.1, node-forge enforced an X.509 CA certificate's basicConstraints.pathLenConstraint only when that certificate also carried a keyUsage extension. Exploitation requires a path-length-constrained CA without keyUsage that chains to a root trusted by the application, and an attacker who holds that CA's private key or obtains a subordinate CA certificate from it. The attacker could then construct a chain exceeding the declared path length that still passed pki.verifyCertificateChain(). Public web PKI CA certificates normally include keyUsage; private PKIs with CA certificates created without it are more likely to be affected. This issue is fixed in version 1.4.1.
This page as .md · .json · in your agent: get_signal("CVE-2026-119189")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.