Quick answers
- Is CVE-2026-125336 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125336 being exploited in the wild.
- How severe is CVE-2026-125336?
- High severity, with a CVSS score of 7.4, published 10 November 2026.
- Which products and versions are affected?
- Digital Bazaar Forge before 1.4.3.
- Is there a fix for CVE-2026-125336?
- Yes: fixed in 1.4.3. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-125336 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-125336?
- Check whether you run Digital Bazaar Forge at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- Fixed in: 1.4.3
Technical details
The pki.verifyCertificateChain() function in lib/x509.js does not decode or enforce the X.509 nameConstraints extension (RFC 5280 4.2.1.10) during certificate path validation. A non-critical nameConstraints extension in an intermediate CA certificate is silently ignored, permitting the CA to issue leaf certificates with dNSName or commonName values outside permitted or inside excluded subtrees. Exploitation requires possession of a name-constrained CA's private key that chains to a trusted root, or the ability to obtain out-of-scope certificates from such a CA.
Affected products
- Digital Bazaar Forge before 1.4.3
Timeline
- 2026-11-10: advisory