Technical impact
Node‑forge used by applications that implement TLS processes each record in a TLS stream by making a recursive call per record. An attacker can send thousands of small TLS records in a single input chunk, consuming one JavaScript stack frame for each record. The recursion eventually exceeds the call stack size, causing an uncaught exception and halting the TLS session, which results in a denial of service to the affected Node.js process. The weakness is an uncontrolled recursion identified as CWE‑674 and CWE‑770, and it does not directly expose confidentiality or integrity of data.
Affected Systems
Applications that incorporate the digitalbazaar:forge (node‑forge) library and use the forge.tls.createConnection() API are vulnerable when running any version older than 1.4.1. The issue applies to Node.js projects that rely on it for TLS support and has not been fixed in earlier releases.
Risk and Exploitability
The CVSS score of 7.5 classifies this bug as high severity, and there is no evidence of a publicly known exploit or listing in the CISA KEV catalog. The EPSS score is not available, but the vulnerability can be exploited remotely by an attacker who can initiate TLS traffic to the target. Based on the description, it is inferred that the attacker can initiate TLS traffic to the target. The attack requires the ability to send crafted TLS records, which is typically achievable from a client behind the attacker's control. The lack of a public exploit mitigates immediate risk, yet the high CVSS indicates that once exploited it can cause a serious service disruption.
Github GHSA