Quick answers
- Is CVE-2026-125333 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-125333 being exploited in the wild.
- How severe is CVE-2026-125333?
- Medium severity, with a CVSS score of 5.9, published 10 November 2026.
- Which products and versions are affected?
- Digital Bazaar Forge 0.1.2 through 1.4.2; node-forge (npm) >= 0.1.2, <= 1.4.2, SEMVER:introduced=0.1.2,fixed=1.4.3.
- Is there a fix for CVE-2026-125333?
- Yes. node-forge (npm): upgrade to 1.4.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-125333 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-125333?
- Check whether you run Digital Bazaar 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.3 or later
npm install node-forge@1.4.3
Technical details
The vulnerability is a ReDoS (Regular Expression Denial of Service) in the _trimString() function used by forge.http to remove trailing whitespace from response header and cookie values. The regex `/\s*$/` exhibits quadratic time complexity when processing a long run of whitespace followed by a non-whitespace character. An attacker controlling a server or intercepting network traffic can cause readHeader() or getCookies() to repeatedly scan input and block the event loop; this only affects applications using forge.http with a socket pool to communicate with untrusted servers.
Affected products
- Digital Bazaar Forge 0.1.2 through 1.4.2
Identifiers
- CVE-2026-125333
- GHSA-6cv4-p8m7-4r25
Timeline
- 2026-11-10: advisory
- 2026-11-04: patched