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-61374 Overview
CVE-2026-61374 is an Allocation of Resources Without Limits or Throttling vulnerability [CWE-770] in the Apache Thrift Java bindings. The flaw affects all versions of Apache Thrift prior to 0.25.0. A remote attacker with low privileges can send crafted input over the network that forces the Java runtime to allocate unbounded memory, leading to a denial-of-service condition against services built on Thrift. The Apache Thrift project has released version 0.25.0 to address the issue.
Critical Impact
Remote attackers can trigger uncontrolled resource allocation in Apache Thrift Java services, exhausting memory and causing denial of service on affected endpoints.
Affected Products
- Apache Thrift Java bindings, all versions before 0.25.0
- Java applications and services using Apache Thrift for RPC serialization
- Downstream frameworks and products that embed vulnerable Thrift Java libraries
Discovery Timeline
- 2026-10-02 - CVE-2026-61374 published to the National Vulnerability Database
- 2026-10-03 - Last updated in NVD database
Technical Details for CVE-2026-61374
Vulnerability Analysis
The vulnerability resides in the Java bindings of Apache Thrift, a cross-language RPC and serialization framework. Thrift decodes binary protocol messages that embed length prefixes describing the size of upcoming fields, lists, maps, sets, and binary blobs. The Java bindings allocated memory based on these attacker-controlled length values without enforcing an upper bound.
An attacker who can reach a Thrift service can send a small message that declares an extremely large collection or buffer. The Java deserializer honors that declaration and attempts to preallocate corresponding memory structures. The resulting allocation exhausts heap memory, triggers OutOfMemoryError, and renders the service unresponsive.
The weakness maps to CWE-770: Allocation of Resources Without Limits or Throttling. Impact is confined to availability; the issue does not expose data or permit code execution.
Root Cause
The Thrift Java protocol readers trusted length and size fields present in incoming serialized data. Without a configurable maximum message size or container cardinality check, a single crafted frame could request allocations larger than available heap. Version 0.25.0 introduces bounds checks that reject oversized declarations before memory is reserved.
Attack Vector
Exploitation requires network access to a Thrift endpoint and low-level authenticated access, consistent with the published attack metrics. The attacker crafts a Thrift message whose header advertises an oversized list, map, set, string, or binary field. On receipt, the Java server attempts the allocation and crashes or stalls. Repeated requests sustain the denial of service.
No verified public exploit or proof-of-concept code is listed in NVD for this issue. See the Apache Mailing List Discussion and Apache Mailing List Update for upstream details.
Detection Methods for CVE-2026-61374
Indicators of Compromise
- Repeated java.lang.OutOfMemoryError: Java heap space entries in logs of services that terminate Thrift transports (TBinaryProtocol, TCompactProtocol, TFramedTransport).
- Sudden spikes in Java heap usage, full garbage collection cycles, or process restarts on Thrift server JVMs following inbound RPC traffic.
- Short-lived TCP sessions to Thrift listener ports that terminate immediately after the initial frame is read.
Detection Strategies
- Inventory Java applications and container images for libthrift versions below 0.25.0 using software composition analysis.
- Inspect Thrift server logs for malformed message exceptions such as TProtocolException paired with abnormally large reported field sizes.
- Correlate inbound request size, source IP, and subsequent JVM restarts to identify abusive clients.
Monitoring Recommendations
- Alert on JVM memory saturation metrics (heap_used / heap_max > 0.9) on hosts running Thrift services.
- Track process restart counts and crash loops for Thrift-based microservices in orchestration platforms such as Kubernetes.
- Enable network flow logging on Thrift listener ports and baseline normal payload sizes to flag anomalies.
How to Mitigate CVE-2026-61374
Immediate Actions Required
- Upgrade the Apache Thrift Java library to version 0.25.0 or later in all affected applications and rebuild dependent artifacts.
- Audit transitive dependencies in Maven and Gradle projects to confirm no shaded or relocated copies of vulnerable libthrift remain.
- Restrict network exposure of Thrift endpoints to trusted clients using firewalls, service mesh policies, or mutual TLS.
Patch Information
The Apache Thrift project fixed this issue in version 0.25.0. Users are recommended to upgrade immediately. Refer to the Apache Mailing List Discussion and the follow-up Apache Mailing List Update for release notes and upstream guidance.
Workarounds
- Place Thrift services behind a reverse proxy or API gateway that enforces maximum request body size.
- Reduce the JVM maximum heap and enable fast-fail restart policies so a single abusive request does not degrade shared infrastructure.
- Require authenticated clients and rate-limit requests at the network layer until the 0.25.0 upgrade is deployed.
# Configuration example: upgrade Apache Thrift Java binding in Maven
# pom.xml dependency update
<dependency>
<groupId>org.apache.thrift</groupId>
<artifactId>libthrift</artifactId>
<version>0.25.0</version>
</dependency>
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

