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-94648 Overview
CVE-2026-94648 is an uncontrolled resource allocation vulnerability [CWE-770] in the Apache Thrift Dart language bindings. The flaw affects all versions of Apache Thrift prior to 0.25.0. A remote attacker can send crafted Thrift messages that cause the Dart binding to allocate resources without any upper bound or throttling control. The result is availability loss on services that parse untrusted Thrift input using the Dart library. The Apache Thrift project has released version 0.25.0, which fixes the issue.
Critical Impact
Unauthenticated network-based attackers can exhaust memory or processing resources in Dart-based Thrift servers, resulting in denial-of-service conditions against RPC endpoints.
Affected Products
- Apache Thrift Dart bindings, all versions before 0.25.0
- Dart applications and services using Thrift for RPC serialization
- Downstream frameworks embedding vulnerable Thrift Dart bindings
Discovery Timeline
- 2026-10-02 - CVE-2026-94648 published to NVD
- 2026-10-05 - Last updated in NVD database
Technical Details for CVE-2026-94648
Vulnerability Analysis
The vulnerability is categorized under CWE-770: Allocation of Resources Without Limits or Throttling. Apache Thrift is a cross-language RPC and serialization framework. The Dart binding deserializes incoming messages containing length-prefixed fields such as lists, sets, maps, and binary blobs. The Dart implementation accepts attacker-supplied size fields and allocates container capacity based on those values before verifying that the underlying transport contains enough data. An attacker can send a small message that declares extremely large element counts, forcing the parser to allocate large structures. Repeated requests amplify the condition into memory or CPU exhaustion. Impact is limited to availability; confidentiality and integrity are not affected.
Root Cause
The root cause is missing input validation on size and length fields during Thrift message decoding in the Dart bindings. The parser trusts header-declared sizes without bounding them against transport length, available memory, or a configured maximum. This matches the CWE-770 pattern of allocating resources driven by untrusted input.
Attack Vector
Exploitation is remote and unauthenticated. The attacker needs network reachability to a Thrift endpoint using the Dart binding. A single crafted frame declaring oversized collections or binary payloads can trigger a large allocation. Sustained traffic produces a reliable denial-of-service outcome against the target process. See the Apache Thread Discussion and Apache Security Discussion for upstream details.
// No verified proof-of-concept code is publicly available.
// See upstream Apache references for technical specifics.
Detection Methods for CVE-2026-94648
Indicators of Compromise
- Sudden spikes in resident memory consumption by Dart processes hosting Thrift endpoints
- Repeated OOM-kill events or process restarts tied to RPC listener services
- Short, malformed, or truncated Thrift frames with disproportionately large declared field sizes
- Elevated CPU usage during Thrift message deserialization with no corresponding business workload
Detection Strategies
- Inspect RPC gateways and reverse proxies for Thrift frames where the declared container size greatly exceeds the frame body size
- Instrument the Dart binding or wrapper code to log allocations above a defined threshold during deserialization
- Correlate process crash telemetry with inbound Thrift traffic volume to identify resource-exhaustion patterns
Monitoring Recommendations
- Alert on repeated restarts of Dart-based Thrift services within short time windows
- Monitor per-connection byte-to-allocation ratios at the application layer
- Track EPSS scoring and vendor advisories for exploit-availability changes; the current EPSS value is 0.426%
How to Mitigate CVE-2026-94648
Immediate Actions Required
- Upgrade Apache Thrift Dart bindings to version 0.25.0 or later across all build pipelines and deployed services
- Inventory Dart applications that import the Thrift package and confirm the resolved transitive version
- Place rate limits and request-size caps in front of exposed Thrift endpoints until patching completes
Patch Information
Apache Thrift version 0.25.0 resolves the issue by enforcing bounds during deserialization in the Dart bindings. Upgrade the thrift dependency in pubspec.yaml and rebuild all consuming Dart applications. Refer to the Apache Thread Discussion and the Apache Security Discussion for upstream guidance.
Workarounds
- Enforce a maximum message size at the transport or framed-transport layer in front of the Dart service
- Terminate TLS and apply request validation at a reverse proxy that can drop oversized or malformed Thrift frames
- Restrict Thrift endpoints to authenticated internal networks until upgrading to 0.25.0
- Apply process-level memory limits (for example, cgroup memory.max) to contain exhaustion attempts
# Update the Dart package to the fixed release
dart pub upgrade thrift
# Verify the resolved version is 0.25.0 or later
dart pub deps | grep 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

