New from Wiz Research: Critical NGINX flaw. Understand the risk and impact.
Vulnerability DatabaseCVE-2026-125333

CVE-2026-125333: 
NixOS vulnerability analysis and mitigation

Overview

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).

Technical details

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).

Impact

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).

Exploitability

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).

Exploitation steps

  1. Identify target applications: Locate applications that explicitly load 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.
  2. Position as malicious server or on-path attacker: Either operate a server that the target application connects to, or perform a man-in-the-middle attack to intercept and modify HTTP responses in transit.
  3. Craft a malicious HTTP response header: Construct an HTTP response containing a header value with a very long run of whitespace characters (tabs and/or spaces) followed by a non-whitespace character. For example, generate a string of ~80,000 alternating tab-space characters: var ws = new Array(40001).join('\t ');
  4. Deliver the malicious response: Send the crafted response to the target client: 'HTTP/1.1 200 OK\r\nX-A: a' + ws + 'X\r\n\r\n'
  5. Trigger event loop blocking: When the client calls 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).

Indicators of compromise

  • Network: Unusually large HTTP response headers (tens of kilobytes to megabytes in a single header value) received by a Node.js application using forge.http; responses containing headers with abnormally long whitespace sequences before a non-whitespace character.
  • Process: Node.js process becoming unresponsive or exhibiting very high CPU usage for extended periods (seconds to minutes) during HTTP response parsing; event loop lag metrics spiking significantly.
  • Logs: Application logs showing timeouts or dropped requests coinciding with connections to external servers; absence of log output during periods when the event loop is blocked.

Mitigation and workarounds

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).

Community reactions

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).

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Ubuntu

Unknown

focal (esm-apps)

node-node-forge

Unknown

jammy

node-node-forge

Unknown

jammy (esm-apps)

node-node-forge

Unknown

RHEL / CentOS

Affected

RHEL 8

pcs.src

Affected

RHEL 9

pcs.src

Affected

RHEL 10

pcs.src

Affected

Source: This report was generated using AI

Related NixOS vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-125336HIGH7.4
  • Grafana logoGrafana
  • grafana-prometheus
NoYesNov 10, 2026
CVE-2026-125334MEDIUM5.9
  • Grafana logoGrafana
  • jitsucom-jitsu
NoYesNov 10, 2026
CVE-2026-125333MEDIUM5.9
  • NixOS logoNixOS
  • wazuh-dashboard-fips
NoYesNov 10, 2026
CVE-2026-125332MEDIUM5.9
  • NixOS logoNixOS
  • gitlab-rails-ce-19.5
NoYesNov 10, 2026
CVE-2026-125335LOW3.7
  • NixOS logoNixOS
  • dotstatsuite-supercore
NoYesNov 10, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management