Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-66031: CWE-674: Uncontrolled Recursion in digitalbazaar forge

0
High
VulnerabilityCVE-2025-66031cvecve-2025-66031cwe-674
Published: Wed Nov 26 2025 (11/26/2025, 22:23:26 UTC)
Source: CVE Database V5
Vendor/Project: digitalbazaar
Product: forge

Description

Forge (also called `node-forge`) is a native implementation of Transport Layer Security in JavaScript. An Uncontrolled Recursion vulnerability in node-forge versions 1.3.1 and below enables remote, unauthenticated attackers to craft deep ASN.1 structures that trigger unbounded recursive parsing. This leads to a Denial-of-Service (DoS) via stack exhaustion when parsing untrusted DER inputs. This issue has been patched in version 1.3.2.

AI-Powered Analysis

AILast updated: 12/03/2025, 23:46:40 UTC

Technical Analysis

The vulnerability identified as CVE-2025-66031 affects the digitalbazaar forge library, commonly known as node-forge, which is a JavaScript implementation of Transport Layer Security (TLS) and cryptographic functions. The flaw is categorized under CWE-674 (Uncontrolled Recursion) and exists in versions 1.3.1 and earlier. The root cause is the lack of bounds checking on the recursion depth when parsing ASN.1 structures encoded in DER format. Attackers can craft malicious ASN.1 inputs with excessive nesting levels, causing the parser to recurse indefinitely until the call stack is exhausted. This results in a Denial-of-Service (DoS) condition by crashing or hanging the application that uses the vulnerable library. The vulnerability can be exploited remotely without any authentication or user interaction, simply by sending specially crafted DER data to the affected system. This makes it highly accessible to attackers. The issue was addressed in version 1.3.2 of node-forge by implementing recursion depth limits or other parsing safeguards to prevent stack exhaustion. No known exploits have been reported in the wild yet, but the high CVSS score of 8.7 indicates a serious risk. The vulnerability impacts any application or service that relies on node-forge for TLS or cryptographic operations, including web servers, client-side applications, and other JavaScript-based systems that parse ASN.1 data.

Potential Impact

For European organizations, this vulnerability poses a significant risk of service disruption due to Denial-of-Service attacks. Since node-forge is widely used in JavaScript environments for TLS and cryptographic functions, affected applications could become unresponsive or crash when processing malicious ASN.1 inputs. This can lead to downtime, loss of availability, and potential cascading effects on dependent services. Industries relying heavily on secure communications, such as finance, healthcare, and government, may face operational interruptions. Additionally, the unauthenticated nature of the exploit means attackers can launch DoS attacks without prior access, increasing the threat surface. The impact is particularly critical for cloud services, web applications, and APIs that accept or process ASN.1 encoded data. Although no data confidentiality or integrity breach is indicated, the loss of availability alone can cause reputational damage and financial losses. Organizations using older versions of node-forge in their software stacks should prioritize remediation to avoid exploitation.

Mitigation Recommendations

The primary mitigation is to upgrade all instances of the digitalbazaar forge (node-forge) library to version 1.3.2 or later, where the vulnerability has been patched. Organizations should audit their software dependencies to identify and update any affected versions. Additionally, implement input validation to restrict the maximum recursion depth or nesting level of ASN.1 structures before parsing. Employ runtime monitoring and anomaly detection to identify unusual parsing behavior or excessive resource consumption indicative of an attack. For web-facing services, consider deploying Web Application Firewalls (WAFs) with rules to detect and block malformed ASN.1 DER payloads. Developers should review and harden any custom ASN.1 parsing code to prevent similar recursion issues. Finally, maintain an incident response plan to quickly address potential DoS incidents and ensure system redundancy to minimize downtime.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2025-11-21T01:08:02.614Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 692781c3d322a87b22e508d8

Added to database: 11/26/2025, 10:40:03 PM

Last enriched: 12/3/2025, 11:46:40 PM

Last updated: 1/11/2026, 3:29:32 AM

Views: 327

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats