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-94639 Overview
CVE-2026-94639 is a denial of service vulnerability in the Apache Thrift Java bindings. The flaw stems from improper handling of exceptional conditions, allocation of resources without limits or throttling, and an uncaught exception [CWE-248]. Remote attackers can send crafted input over the network to trigger unhandled exceptions or exhaust resources in services that use the affected Java bindings. The issue affects all Apache Thrift versions prior to 0.25.0. The Apache Software Foundation recommends upgrading to version 0.25.0, which fixes the issue.
Critical Impact
Unauthenticated remote attackers can crash or degrade availability of Java services built on vulnerable Apache Thrift bindings without any user interaction.
Affected Products
- Apache Thrift Java bindings, all versions before 0.25.0
- Java applications and services embedding affected Thrift client or server bindings
- Downstream frameworks that package vulnerable Thrift Java libraries as a transitive dependency
Discovery Timeline
- 2026-10-02 - CVE-2026-94639 published to the National Vulnerability Database
- 2026-10-05 - Last updated in NVD database
Technical Details for CVE-2026-94639
Vulnerability Analysis
Apache Thrift is a cross-language serialization and remote procedure call (RPC) framework. The Java bindings implement protocol parsers, transports, and server runtimes that deserialize untrusted bytes from network peers. In versions before 0.25.0, specific code paths fail to properly handle exceptional conditions during message parsing, and they allocate memory or other resources based on attacker-controlled fields without enforcing bounds. An attacker who can reach a Thrift endpoint can submit a malformed or oversized payload that either raises an uncaught exception propagating out of the server worker or forces the runtime to reserve excessive memory. Either outcome results in loss of service availability. The CVSS v4.0 vector reflects a network attack vector with no privileges, no user interaction, and high availability impact only; confidentiality and integrity are not affected.
Root Cause
The root cause is tracked under [CWE-248: Uncaught Exception], combined with missing resource allocation limits. Protocol decode routines in the Java bindings do not validate size or structural fields before performing allocations, and they do not catch runtime exceptions at the appropriate boundary. When invalid input is processed, the exception escapes the handler thread or the preallocation exhausts the Java Virtual Machine (JVM) heap.
Attack Vector
Exploitation requires only network reachability to a vulnerable Thrift Java service. The attacker transmits a crafted Thrift message that triggers the parsing fault. No authentication or user interaction is required. Repeated requests can render the service unresponsive or trigger process termination, depending on how the host application supervises worker threads. See the Apache Mailing List Discussion and the Apache Mailing List Update for upstream technical details.
Detection Methods for CVE-2026-94639
Indicators of Compromise
- Repeated java.lang.OutOfMemoryError or uncaught TException and TProtocolException stack traces in Thrift server logs
- Sudden spikes in JVM heap usage or garbage collection activity on hosts running Thrift Java services
- Abrupt termination or restart loops of application processes exposing Thrift endpoints
- Unusual bursts of short-lived TCP connections targeting Thrift listener ports from a limited set of source addresses
Detection Strategies
- Inventory Java applications and transitive dependencies to identify any libthrift version below 0.25.0
- Correlate application crash events with inbound network traffic volume to Thrift ports
- Enable verbose exception logging on Thrift server handlers to capture parser-level failures
- Monitor JVM metrics such as heap pressure, thread death counts, and worker pool saturation for anomalies
Monitoring Recommendations
- Forward application and JVM logs into a centralized analytics platform and alert on repeated Thrift protocol exceptions
- Track process uptime and restart frequency for services that terminate Thrift endpoints
- Baseline normal request sizes and alert when inbound Thrift payloads exceed expected thresholds
How to Mitigate CVE-2026-94639
Immediate Actions Required
- Upgrade the Apache Thrift Java bindings to version 0.25.0 or later across all affected services
- Audit build manifests such as pom.xml and build.gradle for direct and transitive libthrift dependencies
- Restrict network exposure of Thrift endpoints to trusted clients using network segmentation and firewall rules
- Deploy rate limiting and connection quotas in front of Thrift listeners to blunt resource exhaustion attempts
Patch Information
The Apache Software Foundation addressed CVE-2026-94639 in Apache Thrift 0.25.0. Users of all prior versions are instructed to upgrade. Refer to the Apache Mailing List Discussion and Apache Mailing List Update for release context.
Workarounds
- Place Thrift services behind an authenticated reverse proxy or service mesh that enforces maximum message size
- Configure application-level supervision to recover worker threads that die from uncaught exceptions
- Apply JVM memory limits and container resource quotas to contain the blast radius of allocation-based attacks
- Temporarily disable or firewall non-essential Thrift endpoints until the upgrade to 0.25.0 is complete
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

