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-94644 Overview
CVE-2026-94644 is a resource allocation vulnerability in the Apache Thrift PHP bindings. The flaw affects all versions of Apache Thrift prior to 0.25.0 and is tracked under CWE-770: Allocation of Resources Without Limits or Throttling. Remote attackers can send crafted Thrift messages that cause excessive resource consumption in PHP processes handling the deserialization. The vulnerability requires no authentication and no user interaction, and it targets the availability of affected services. The Apache Thrift project has released version 0.25.0 to remediate the issue.
Critical Impact
Unauthenticated remote attackers can trigger resource exhaustion in Apache Thrift PHP services, causing denial-of-service conditions against applications that process untrusted Thrift payloads.
Affected Products
- Apache Thrift PHP bindings, all versions before 0.25.0
- PHP applications using Apache Thrift for RPC or serialization
- Services exposing Thrift endpoints to untrusted networks
Discovery Timeline
- 2026-10-02 - CVE-2026-94644 published to NVD
- 2026-10-05 - Last updated in NVD database
Technical Details for CVE-2026-94644
Vulnerability Analysis
The vulnerability resides in how the Apache Thrift PHP bindings allocate memory and other resources when parsing incoming messages. The library trusts length and container-size fields encoded in the Thrift wire format without enforcing upper bounds relative to actual payload size. An attacker can declare very large collections, strings, or nested structures in a small request, causing the PHP runtime to pre-allocate buffers or build data structures that exhaust memory and CPU. The result is a denial-of-service condition that can crash PHP workers or make the host service unresponsive. Because Thrift bindings are commonly used in high-throughput backend RPC paths, a single request can impact many downstream consumers.
Root Cause
The root cause is missing validation of resource limits during Thrift message decoding in the PHP bindings. Protocol handlers accept size prefixes and recursion depths from the wire without comparing them to the available payload bytes or configured ceilings, which matches the CWE-770 pattern of allocation without throttling.
Attack Vector
Exploitation is network-based and does not require authentication or user interaction. An attacker submits a crafted Thrift message, such as one declaring an oversized list, map, set, or binary field, to any PHP endpoint that deserializes Thrift payloads. The PHP process attempts to allocate structures matching the declared sizes and either exhausts memory, consumes excessive CPU, or triggers a fatal error. Repeated requests amplify the impact across worker processes.
No verified public proof-of-concept code is available. Refer to the Apache Mailing List Update and the Apache Mailing List Discussion for authoritative technical context.
Detection Methods for CVE-2026-94644
Indicators of Compromise
- Repeated PHP worker crashes or fatal Allowed memory size exhausted errors in application logs during Thrift request handling.
- Sudden spikes in memory and CPU consumption on PHP-FPM or CLI workers correlating with inbound Thrift traffic.
- Short, low-byte requests to Thrift endpoints followed by abnormally long processing times or timeouts.
Detection Strategies
- Inventory services that import the Apache Thrift PHP bindings and verify the installed version against 0.25.0.
- Instrument Thrift servers to log decoded container sizes and reject or flag messages that declare unusually large lists, maps, or strings.
- Correlate web and RPC gateway logs with PHP worker restarts to surface request patterns that precede resource exhaustion events.
Monitoring Recommendations
- Alert on memory_limit breaches, OOM-killer events, and PHP-FPM worker respawn rates on hosts running Thrift services.
- Monitor request-size to processing-time ratios on Thrift endpoints to detect low-byte, high-cost messages.
- Track dependency manifests such as composer.lock for apache/thrift versions below 0.25.0.
How to Mitigate CVE-2026-94644
Immediate Actions Required
- Upgrade the Apache Thrift PHP bindings to version 0.25.0 or later across all affected services.
- Restrict exposure of Thrift endpoints so that only trusted clients and networks can reach them while patching is in progress.
- Enforce request-size limits at the ingress or reverse-proxy layer to bound the maximum Thrift message size.
Patch Information
Apache has released Apache Thrift 0.25.0, which addresses the resource-allocation flaw in the PHP bindings. Update the apache/thrift dependency in composer.json and redeploy. Confirm patch adoption through the Apache Mailing List Update.
Workarounds
- Place Thrift services behind an authenticated gateway or mTLS boundary to reduce the unauthenticated attack surface.
- Lower the PHP memory_limit and max_execution_time on Thrift workers so that abusive requests fail fast without destabilizing the host.
- Add application-layer validation that rejects Thrift messages exceeding expected field counts, string lengths, or nesting depth before invoking the deserializer.
# Upgrade Apache Thrift PHP bindings to the fixed release
composer require apache/thrift:^0.25.0
composer update apache/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

