Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-94645 Overview
CVE-2026-94645 is a resource exhaustion vulnerability in the Apache Thrift Node.js bindings. The flaw stems from improper validation of a quantity specified in input, which permits unbounded resource allocation during message processing. The weakness is classified as [CWE-770] Allocation of Resources Without Limits or Throttling. All Apache Thrift releases prior to 0.25.0 are affected, and the Apache Thrift project has released version 0.25.0 to address the issue.
Critical Impact
A remote, unauthenticated attacker can send crafted Thrift messages to a Node.js service and trigger excessive resource allocation, resulting in denial of service against the target process.
Affected Products
- Apache Thrift Node.js bindings prior to version 0.25.0
- Node.js services and RPC endpoints that embed vulnerable Apache Thrift libraries
- Downstream applications bundling affected Apache Thrift Node.js packages
Discovery Timeline
- 2026-10-02 - CVE-2026-94645 published to NVD
- 2026-10-05 - Last updated in NVD database
Technical Details for CVE-2026-94645
Vulnerability Analysis
The Apache Thrift Node.js bindings parse incoming messages that include length-prefixed fields describing the size of upcoming containers such as lists, sets, maps, and binary blobs. The vulnerable code paths trust the declared size and preallocate buffers or data structures before verifying that the remaining payload actually contains that much data. An attacker who controls the serialized input can declare an extremely large element count while sending only a few bytes on the wire.
The Node.js runtime then attempts to satisfy the allocation, consuming heap memory and CPU cycles. Repeated requests exhaust available memory, trigger garbage collector thrashing, or crash the Node.js process with an out-of-memory condition. The attack succeeds without authentication because Thrift servers typically expose RPC endpoints before any application-level authentication is enforced.
Root Cause
The root cause is the absence of an upper bound on container and binary field sizes during deserialization in the Node.js bindings. The protocol reader honors the attacker-controlled length value and requests the corresponding memory allocation. Without a configured maximum message size or container size, the parser cannot distinguish a legitimate large message from a malicious size declaration.
Attack Vector
Exploitation requires network access to a Thrift service built on the Node.js bindings. The attacker crafts a serialized Thrift message, either in binary or compact protocol form, that specifies an oversized container or binary field length. The attacker sends the message to the target endpoint and may repeat it across multiple connections to amplify impact. No credentials or user interaction are required. See the Apache Mailing List Thread and the follow-up discussion for additional technical context.
Detection Methods for CVE-2026-94645
Indicators of Compromise
- Repeated Node.js process restarts or out-of-memory crashes on hosts exposing Thrift endpoints
- Sudden spikes in resident set size (RSS) or heap usage in Thrift server processes
- Short-lived TCP connections to Thrift ports that terminate before completing an RPC exchange
- Log entries showing deserialization errors referencing oversized containers or binary fields
Detection Strategies
- Inspect the installed Apache Thrift Node.js package version and flag any release prior to 0.25.0
- Monitor Thrift server telemetry for anomalous message sizes or truncated payloads that fail parsing
- Correlate memory pressure alerts on Node.js hosts with inbound traffic on Thrift listener ports
- Deploy network signatures that identify Thrift messages declaring container lengths above expected business thresholds
Monitoring Recommendations
- Centralize Node.js process metrics (heap, RSS, event loop lag) and alert on sustained growth
- Capture and retain Thrift RPC access logs for retrospective analysis of DoS attempts
- Track application restart counts and OOM-killer events on hosts running Thrift services
- Baseline normal RPC payload sizes and alert on statistical outliers
How to Mitigate CVE-2026-94645
Immediate Actions Required
- Upgrade Apache Thrift Node.js bindings to version 0.25.0 or later across all affected services
- Audit dependency manifests (package.json, package-lock.json, yarn.lock) for transitive Thrift dependencies
- Restrict network exposure of Thrift endpoints to trusted clients using firewalls or service mesh policies
- Add process supervision and memory limits to contain the blast radius of any successful exploitation
Patch Information
The Apache Thrift project fixed the vulnerability in version 0.25.0. Users are advised to upgrade immediately. Release details are available via the referenced Apache Mailing List Thread.
Workarounds
- Enforce a maximum request body size at a reverse proxy or API gateway in front of Thrift services
- Apply container memory limits (for example, --memory in Docker or Kubernetes resource limits) to prevent host-wide impact
- Terminate idle or slow connections aggressively to reduce the window for abuse
- Place Thrift services behind mutual TLS or authenticated transport to limit anonymous access
# Configuration example
# Upgrade Apache Thrift Node.js bindings to the fixed release
npm install thrift@0.25.0 --save
# Verify the installed version
npm ls thrift
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

