
PEACH
Uma estrutura de isolamento de inquilino
CVE-2026-125336 is an X.509 nameConstraints bypass vulnerability in node-forge (also called Forge), a native JavaScript implementation of Transport Layer Security. The flaw exists in pki.verifyCertificateChain() within lib/x509.js, which fails to decode or enforce the X.509 nameConstraints extension (OID 2.5.29.30) during certificate path validation. All versions of node-forge up to and including 1.4.2 are affected; the issue is fixed in version 1.4.3, released November 4, 2026. It carries a CVSS v3.1 base score of 7.4 (High) (GitHub Advisory, Feedly).
The root cause is classified as CWE-295 (Improper Certificate Validation). Specifically, RFC 5280 path validation steps 6.1.3(b) and (c) — which require checking each certificate's names against the permitted and excluded subtrees defined by CA certificates above it — were never implemented in pki.verifyCertificateChain(). Because the nameConstraints extension was not decoded at all, a non-critical instance of the extension is silently ignored: a CA constrained to only .example.com can issue a leaf certificate with CN=evil.com or a subjectAltName dNSName evil.com, and node-forge accepts the chain as valid. Notably, a critical nameConstraints extension was rejected as an unsupported critical extension (safe failure), but the CA/Browser Forum Baseline Requirements historically permitted technically constrained subordinate CAs to mark the extension non-critical, meaning such CAs exist in real-world PKI hierarchies. The attack vector is network-based with high complexity, requiring no privileges or user interaction (GitHub Advisory, Forge PR #1169).
Successful exploitation allows an attacker to obtain TLS certificates that node-forge accepts for arbitrary domain names, effectively defeating the namespace restrictions that a name-constrained CA was intended to enforce. This enables impersonation of any host to applications using forge.tls for TLS peer verification, resulting in high confidentiality and integrity impact (credential theft, man-in-the-middle interception of encrypted traffic, data manipulation). Availability is not directly impacted. The scope is limited to applications that use node-forge for certificate chain validation and trust a root under which a non-critically name-constrained CA exists; chains without nameConstraints are entirely unaffected (GitHub Advisory).
A proof-of-concept is publicly available in the GitHub Security Advisory, including a concrete reproduction scenario and a full PoC script at tests/pocs/GHSA-3cc4-3294-vgjf.js in the patched repository. The advisory was published November 4, 2026, and the CVE was assigned November 10, 2026. There is no evidence of active in-the-wild exploitation at this time, and no threat actor attribution has been reported. The EPSS score is approximately 0.0023 (low probability of exploitation in the near term). The vulnerability is not listed in the CISA KEV catalog. Exploitation requires high complexity — specifically, the attacker must control the private key of a name-constrained CA that chains to a root trusted by the target application, or be able to obtain a certificate issued under such a CA (GitHub Advisory, Feedly).
forge.tls) or certificate chain validation (pki.verifyCertificateChain()), and that trusts a root CA under which a name-constrained intermediate CA with a non-critical nameConstraints extension exists.CN=evil.com with no subjectAltName, or with subjectAltName dNSName evil.com), even though the intermediate's nameConstraints only permits .example.com.[leaf, intermediate] to the target application during a TLS handshake or certificate verification call. On node-forge <= 1.4.2, pki.verifyCertificateChain(caStore, [leaf, intermediate]) returns true because the nameConstraints extension is not decoded or enforced.evil.com, enabling man-in-the-middle interception, credential harvesting, or other attacks against the application's TLS-protected communications (GitHub Advisory).subjectAltName dNSName or subject commonName falls outside the permittedSubtrees or inside the excludedSubtrees of an intermediate CA's nameConstraints extension.node-forge npm package at version <= 1.4.2 in package.json or package-lock.json files (GitHub Advisory).The primary remediation is to upgrade node-forge to version 1.4.3 or later, which fully enforces nameConstraints in verifyCertificateChain() for subject DN, rfc822Name, dNSName, directoryName, uniformResourceIdentifier, and iPAddress name types. As a temporary workaround (if upgrading is not immediately possible), pass a custom options.verify callback to pki.verifyCertificateChain() (or a verify callback to forge.tls.createConnection()) that returns an error whenever any CA certificate in the chain contains an extension with OID 2.5.29.30 — this rejects all chains below any name-constrained CA, including valid ones. Organizations should prioritize patching systems where node-forge is used for TLS client operations or certificate chain validation in security-sensitive contexts (GitHub Advisory, Forge Release v1.4.3).
The vulnerability was reported by security researcher @bhaswanthc, who also contributed the initial implementation of the fix. The advisory was published by the digitalbazaar maintainer davidlehn on November 4, 2026, alongside four other security fixes bundled in the 1.4.3 release. No significant broader media coverage or notable social media commentary beyond the GitHub advisory and standard CVE tracking databases has been identified at this time (GitHub Advisory, Forge PR #1169).
Corrija a disponibilidade entre as principais distribuições Linux e seus lançamentos.
Origem: Este relatório foi gerado usando IA
Avaliação Gratuita de Vulnerabilidades
Avalie suas práticas de segurança em nuvem em 9 domínios de segurança para avaliar seu nível de risco e identificar lacunas em suas defesas.
Marque uma demonstração personalizada
"A melhor experiência do usuário que eu já vi, fornece visibilidade total para cargas de trabalho na nuvem."
"A Wiz fornece um único painel de vidro para ver o que está acontecendo em nossos ambientes de nuvem."
"Sabemos que se a Wiz identifica algo como crítico, na verdade é."