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-96288 Overview
CVE-2026-96288 is an uncontrolled recursion vulnerability [CWE-674] in the Apache Thrift Erlang bindings. The flaw allows a remote attacker to send crafted input that triggers unbounded recursion and uncontrolled resource allocation. The condition exhausts process resources on servers that deserialize untrusted Thrift messages. Apache Thrift versions prior to 0.25.0 are affected, and the project recommends upgrading to 0.25.0 to remediate the issue.
Critical Impact
A network-reachable attacker can cause denial of service against Erlang-based Thrift services by sending specially crafted messages that trigger uncontrolled recursion and resource consumption.
Affected Products
- Apache Thrift Erlang bindings, all versions before 0.25.0
- Erlang services that deserialize untrusted Thrift messages using the affected bindings
- Downstream applications bundling vulnerable Apache Thrift Erlang libraries
Discovery Timeline
- 2026-10-02 - CVE-2026-96288 published to NVD
- 2026-10-02 - Last updated in NVD database
Technical Details for CVE-2026-96288
Vulnerability Analysis
The Apache Thrift Erlang bindings parse incoming messages that encode nested data structures such as lists, maps, sets, and structs. The affected parser recurses into nested fields without enforcing a depth limit or bounding the resources allocated during decoding. An attacker who can send a Thrift message to a service can submit arbitrarily nested structures that drive recursion depth and memory allocation beyond safe limits.
The weakness is tracked as [CWE-674 Uncontrolled Recursion]. Because the parser is invoked before application-level validation, denial of service occurs during protocol decoding. Erlang processes handling the request can grow their stacks and heaps until the scheduler stalls, the process is killed, or the host runs out of memory. Service availability degrades even when only a small number of malicious messages are sent.
Remediation requires upgrading to Apache Thrift 0.25.0, which introduces bounds on nested structure handling in the Erlang bindings. See the Apache Mailing List Discussion and the Apache Mailing List Thread for the project announcement.
Root Cause
The root cause is missing recursion depth enforcement and missing allocation limits in the Erlang Thrift decoder. The decoder treats nesting depth as implicit input and does not validate it against a maximum. Resource allocation during decoding scales linearly or worse with attacker-controlled structure depth.
Attack Vector
The attack vector is the network. An unauthenticated attacker sends a crafted Thrift payload to any endpoint that uses the vulnerable Erlang bindings. The crafted payload embeds deeply nested containers that force the decoder into excessive recursion. No user interaction is required, and no credentials are needed when the service accepts anonymous Thrift traffic.
The vulnerability affects availability only. Confidentiality and integrity are not impacted according to the CVSS vector published by the Apache Software Foundation.
Detection Methods for CVE-2026-96288
Indicators of Compromise
- Erlang VM processes terminating with system_limit or enomem errors shortly after receiving Thrift traffic
- Spikes in Erlang process heap size or scheduler run queue length during Thrift message decoding
- Repeated Thrift connection attempts from a single source followed by service crashes or restarts
Detection Strategies
- Inspect Thrift message payloads at the application layer for abnormal nesting depth before passing them to the decoder
- Correlate crash dumps from Erlang nodes with inbound Thrift request patterns to identify malicious senders
- Monitor Apache Thrift library versions across the fleet and flag any Erlang service running a version earlier than 0.25.0
Monitoring Recommendations
- Alert on sustained memory or CPU growth in Erlang processes that terminate TCP sessions carrying Thrift traffic
- Track error logs for badarg, stack overflow, or scheduler collapse events tied to Thrift decoding modules
- Record source IP addresses and request sizes for Thrift endpoints to support rate limiting and forensic review
How to Mitigate CVE-2026-96288
Immediate Actions Required
- Upgrade Apache Thrift Erlang bindings to version 0.25.0 or later across all affected services
- Restrict network exposure of Thrift endpoints to trusted clients using firewalls or service mesh policies
- Enforce per-connection message size limits at the load balancer or reverse proxy in front of Thrift services
Patch Information
The Apache Thrift project fixed the issue in version 0.25.0. Upgrade all Erlang services that import the Thrift bindings and redeploy dependent applications. Verify the installed version using the package manager used to vendor Thrift in each service. Refer to the Apache Mailing List Discussion for release details.
Workarounds
- Place an application-aware proxy in front of vulnerable services to reject Thrift messages exceeding a safe nesting depth
- Apply strict connection rate limits and request size caps on Thrift listeners until patching completes
- Isolate Thrift workers in supervised Erlang applications so recursive crashes do not take down the entire node
# Configuration example: reject oversized Thrift payloads at the proxy
# Example nginx stream rule capping Thrift message size to 64 KiB
stream {
server {
listen 9090;
proxy_pass thrift_backend;
proxy_buffer_size 64k;
proxy_connect_timeout 2s;
}
}
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

