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-96990 Overview
CVE-2026-96990 is an Allocation of Resources Without Limits or Throttling vulnerability [CWE-770] affecting the Erlang bindings of Apache Thrift. The flaw exists in all versions of Apache Thrift prior to 0.25.0. A remote, unauthenticated attacker can send crafted Thrift protocol messages that cause the Erlang server to allocate resources without bound, leading to a denial-of-service condition. The Apache Thrift project recommends upgrading to version 0.25.0, which contains the fix.
Critical Impact
Unauthenticated network attackers can exhaust server memory or compute on Erlang-based Apache Thrift services, resulting in service unavailability.
Affected Products
- Apache Thrift Erlang bindings, all versions prior to 0.25.0
- Erlang/OTP applications embedding affected Thrift client or server libraries
- Downstream services that expose Thrift endpoints over untrusted networks
Discovery Timeline
- 2026-10-02 - CVE-2026-96990 published to NVD
- 2026-10-05 - Last updated in NVD database
Technical Details for CVE-2026-96990
Vulnerability Analysis
The Apache Thrift Erlang bindings fail to enforce resource limits when processing incoming protocol messages. Thrift serializes structured data using a compact binary format that encodes field types, container sizes, and string lengths within the payload itself. When a server trusts attacker-supplied size fields without validation, it can be instructed to pre-allocate large buffers, lists, or maps that have no basis in the actual message payload.
Under sustained attack, the Erlang virtual machine (BEAM) consumes memory, scheduler time, and garbage collection cycles. Because the Erlang runtime does not immediately terminate processes exceeding memory thresholds in all configurations, a single malformed request can degrade the entire node. Repeated requests amplify the effect across worker processes.
Root Cause
The root cause is missing throttling and bounds checking on resource allocation driven by untrusted input [CWE-770]. The Erlang binding reads length-prefixed fields from the wire and allocates corresponding structures before validating that the declared size matches the available data. The fix in version 0.25.0 introduces size constraints and validation during deserialization.
Attack Vector
Exploitation requires network access to a Thrift endpoint and no authentication. The attacker crafts a Thrift message in which length prefixes for lists, sets, maps, strings, or binary fields declare very large sizes. The vulnerable server allocates buffers matching those sizes, exhausting memory or CPU. The attack can be launched from any client capable of speaking the Thrift binary or compact protocol. See the Apache Security Discussion and Apache Mailing List Thread for upstream details.
Detection Methods for CVE-2026-96990
Indicators of Compromise
- Sudden spikes in BEAM memory consumption on hosts running Thrift Erlang services
- Unusually large declared field or container sizes in inbound Thrift traffic
- Repeated client disconnects followed by rapid reconnect patterns from a small set of source IPs
- Thrift server processes crashing with system_limit or out-of-memory errors in Erlang crash dumps
Detection Strategies
- Instrument Thrift deserialization paths to log declared sizes exceeding reasonable application thresholds
- Correlate network telemetry with Erlang process memory metrics to identify request-driven allocation spikes
- Alert when BEAM scheduler utilization or garbage collection time rises without a corresponding increase in legitimate request volume
Monitoring Recommendations
- Export Erlang VM metrics such as erlang:memory/0 and erlang:statistics/1 to a central monitoring platform
- Monitor Thrift endpoint request rates, payload sizes, and error ratios per source address
- Capture packet or application logs for forensic review when memory thresholds are breached
How to Mitigate CVE-2026-96990
Immediate Actions Required
- Upgrade Apache Thrift Erlang bindings to version 0.25.0 or later across all services
- Inventory internal and external services exposing Thrift endpoints and prioritize internet-facing instances
- Restrict network access to Thrift ports using firewalls, security groups, or service meshes until patching is complete
- Enable per-process memory limits on BEAM nodes to contain abusive requests
Patch Information
Apache Thrift version 0.25.0 resolves CVE-2026-96990 by introducing resource limits and validation in the Erlang bindings. Rebuild and redeploy any application that statically bundles the Thrift library. Verify the upgraded version is actually loaded at runtime, since Erlang releases may pin older dependencies in rebar.lock or mix.lock files.
Workarounds
- Place a reverse proxy or application-layer gateway in front of Thrift services to cap message size
- Apply Erlang max_heap_size and process memory limits to Thrift worker processes
- Require mutual TLS or network-level authentication so unauthenticated attackers cannot reach the endpoint
- Rate-limit connections per source IP at the load balancer to blunt amplification
# Example: pin Apache Thrift 0.25.0 in rebar.config
{deps, [
{thrift, "0.25.0"}
]}.
# Example: enforce a per-process heap limit in an Erlang supervisor child spec
ChildSpec = #{id => thrift_worker,
start => {thrift_worker, start_link, []},
restart => transient,
shutdown => 5000,
type => worker,
modules => [thrift_worker]},
spawn_opt(fun thrift_worker:loop/0,
[{max_heap_size, #{size => 1048576, kill => true, error_logger => true}}]).
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

