
Cloud Vulnerability DB
A community-led vulnerabilities database
CVE-2026-125333 is a Regular Expression Denial of Service (ReDoS) vulnerability in the forge.http module of node-forge (also called Forge), a native JavaScript TLS implementation. The vulnerability affects node-forge versions 0.1.2 through 1.4.2 and was reported by @manus-pi, with the advisory published on November 4, 2026, and added to the GitHub Advisory Database on November 10, 2026. A malicious server or on-path attacker can craft HTTP response headers or cookies with long whitespace sequences to block the Node.js event loop or browser tab for minutes. It carries a CVSS v3.1 base score of 5.9 (Moderate) (Github Advisory, Feedly).
The root cause is CWE-1333 (Inefficient Regular Expression Complexity): the _trimString() function in lib/http.js uses str.replace(/\s*$/, '') to remove trailing whitespace from response header values and cookie names/values. On a string of n whitespace characters followed by a non-whitespace character, the regex engine attempts a match at each of the n positions and scans the remainder of the run each time, resulting in O(n²) work. forge.http calls _trimString() on every response header value via response.readHeader() and on cookie names/values via response.getCookies(), with no limit on header size — on Node.js 24, an 80 KB header takes ~4 seconds and a 1 MB header ~10 minutes to parse. Exploitation requires the attacker to control or intercept HTTP responses delivered to an application that explicitly loads forge.http with a socket pool; forge.http is not included in the default require('node-forge') import (Github Advisory, Forge Commit).
Successful exploitation causes a denial-of-service condition by blocking the Node.js event loop or browser tab for an extended period (potentially minutes), preventing the affected process from handling any other requests or tasks during that time. There is no confidentiality or integrity impact — the vulnerability is purely an availability issue. Only applications that explicitly use forge.http with a socket pool to communicate with untrusted servers are affected; the attack surface is therefore limited but real for those deployments (Github Advisory, Feedly).
A proof-of-concept exploit is publicly available in the GitHub security advisory, consisting of a short JavaScript snippet that triggers the quadratic regex behavior by feeding a crafted whitespace-heavy header to forge.http.readHeader(). The EPSS score is approximately 0.56% (47th percentile), and there is no evidence of in-the-wild exploitation at this time. The vulnerability is classified as poc exploitation status by NVD SSVC, is not automatable, and has not been added to the CISA KEV catalog (Github Advisory, Feedly).
forge.http (part of the forge.all bundle) and use it with a socket pool to communicate with an external server — these are the only affected deployments.var ws = new Array(40001).join('\t ');'HTTP/1.1 200 OK\r\nX-A: a' + ws + 'X\r\n\r\n'response.readHeader() or response.getCookies(), the quadratic regex in _trimString() processes the whitespace run, blocking the Node.js event loop or browser tab for seconds to minutes depending on the payload size (~4 seconds for 80 KB, ~10 minutes for 1 MB on Node.js 24) (Github Advisory).forge.http; responses containing headers with abnormally long whitespace sequences before a non-whitespace character.The primary remediation is to upgrade node-forge to version 1.4.3 or later, which replaces the quadratic _trimString() regex with a linear loop-based implementation (Forge Release, Forge Commit). As a workaround for applications that cannot immediately upgrade, limit the size of HTTP response headers before passing them to forge.http — for example, by adding a size check in the socket pool's data handler. Additionally, implementing request/response timeouts can bound the duration of any event loop blocking caused by this vulnerability (Github Advisory).
The vulnerability was reported by security researcher @manus-pi and addressed by the node-forge maintainer (@davidlehn) as part of the node-forge 1.4.3 security release, which also fixed four other vulnerabilities including a high-severity x509 nameConstraints bypass. Red Hat tracked the issue via Bugzilla and Microsoft acknowledged it through their security update guide. No significant broader community discussion or media coverage has been identified beyond standard vulnerability database entries (Github Advisory, Forge PR).
Fix availability across major Linux distributions and their releases.
Source: This report was generated using AI
Free Vulnerability Assessment
Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.
Get a personalized demo
"Best User Experience I have ever seen, provides full visibility to cloud workloads."
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
"We know that if Wiz identifies something as critical, it actually is."