Quick answers
- Is CVE-2026-119190 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-119190 being exploited in the wild.
- How severe is CVE-2026-119190?
- High severity, with a CVSS score of 7.4, published 29 October 2026.
- Which products and versions are affected?
- Digital Bazaar Node-Forge before 1.4.1; node-forge (npm) <= 1.4.0, SEMVER:introduced=0,fixed=1.4.1.
- Is there a fix for CVE-2026-119190?
- Yes. node-forge (npm): upgrade to 1.4.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-119190 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-119190?
- Check whether you run Digital Bazaar Node-Forge or node-forge (npm) 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
- node-forge (npm): upgrade to 1.4.1 or later
npm install node-forge@1.4.1
Technical details
node-forge incorrectly parses deprecated OIDs 2.5.29.10 and 2.5.29.13 as basicConstraints and uses the first matching extension name during certificate chain verification instead of strictly checking OID 2.5.29.19. An attacker with a certificate signed by a trusted CA can place a permissive deprecated-OID extension before the genuine basicConstraints extension to bypass the constraint check. The vulnerability requires the issuing CA to copy extensions from a certificate signing request without filtering.
Affected products
- Digital Bazaar node-forge before 1.4.1
Identifiers
- CVE-2026-119190
- GHSA-5x38-2vff-x55p
Timeline
- 2026-10-29: disclosed
- 2026-10-27: patched