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-94655 Overview
CVE-2026-94655 is a resource exhaustion vulnerability in the Apache Thrift Lua bindings. The flaw combines unbounded resource allocation with inefficient algorithmic complexity, allowing a remote attacker to overwhelm services that parse untrusted Thrift messages. All Apache Thrift releases prior to 0.25.0 are affected. The Apache Thrift project assigns this issue to [CWE-407: Inefficient Algorithmic Complexity]. Exploitation requires no authentication and no user interaction, and the attack surface is any network-exposed service built on the Lua bindings. The project recommends upgrading to version 0.25.0, which contains the fix.
Critical Impact
A remote, unauthenticated attacker can send crafted Thrift payloads to the Lua bindings to exhaust CPU and memory, resulting in denial of service of the host application.
Affected Products
- Apache Thrift Lua bindings, all versions before 0.25.0
- Applications and services embedding the vulnerable Lua bindings
- Downstream software that bundles Apache Thrift Lua as a transitive dependency
Discovery Timeline
- 2026-10-02 - CVE-2026-94655 published to NVD
- 2026-10-02 - Last updated in NVD database
Technical Details for CVE-2026-94655
Vulnerability Analysis
The vulnerability resides in how the Apache Thrift Lua bindings parse incoming serialized messages. The parser accepts attacker-controlled size and count fields without enforcing upper bounds. It then allocates structures and performs processing whose cost scales non-linearly with those inputs. A small payload on the wire can therefore translate into a large amount of work on the server. The result is sustained CPU consumption, memory growth, or both, which prevents the application from servicing legitimate traffic. Because Thrift is commonly used as an RPC transport between microservices, a single abusive client can degrade an entire service tier.
Root Cause
Two weaknesses combine in this issue. First, resource allocation is performed on untrusted length fields without throttling or a configured maximum. Second, the processing path exhibits inefficient algorithmic complexity, so increases in input size disproportionately increase processing time. [CWE-407] describes exactly this class of defect, where the asymptotic cost of handling input becomes an attack primitive.
Attack Vector
The attack vector is network based. An attacker sends a crafted Thrift message to any endpoint that deserializes input using the Lua bindings. No credentials and no user interaction are required. Repeated or parallel requests amplify the impact, degrading availability of the targeted service and potentially of co-located workloads sharing the same host. See the Apache Mailing List Announcement and the Apache Mailing List Discussion for project context. No public proof-of-concept exploit code is referenced in the advisory.
Detection Methods for CVE-2026-94655
Indicators of Compromise
- Sustained spikes in CPU or resident memory for processes hosting the Thrift Lua bindings without a corresponding increase in legitimate request volume.
- Thrift RPC requests whose declared collection or string sizes are unusually large compared to normal application traffic baselines.
- Repeated client connections from a single source that terminate with timeouts or out-of-memory errors on the server.
Detection Strategies
- Instrument Thrift servers to log declared field sizes and reject or alert on values that exceed documented application limits.
- Correlate network flow telemetry with process-level resource metrics to identify small requests that produce outsized compute cost.
- Add synthetic health checks that fail fast when request handling latency exceeds a defined threshold, surfacing degradation early.
Monitoring Recommendations
- Track p95 and p99 request handling latency for every Thrift endpoint and alert on sudden deviations.
- Monitor Lua VM memory and garbage collection pressure for services that embed the bindings.
- Forward application and host telemetry into a centralized analytics platform so resource exhaustion patterns are visible across the service tier.
How to Mitigate CVE-2026-94655
Immediate Actions Required
- Inventory all services and container images that include Apache Thrift Lua bindings prior to 0.25.0.
- Upgrade affected deployments to Apache Thrift 0.25.0 and redeploy dependent services.
- Restrict network exposure of Thrift endpoints to trusted clients until patching is complete.
- Apply rate limiting and request size limits at the ingress or service mesh layer.
Patch Information
Apache Thrift 0.25.0 fixes the issue. Upgrade the Thrift Lua bindings to this version in all affected environments. Confirm the fix is applied in both direct dependencies and transitive dependencies pulled in by other packages. Refer to the Apache Mailing List Announcement for release details.
Workarounds
- Place the vulnerable service behind a proxy that enforces maximum request body size and connection concurrency limits.
- Terminate Thrift traffic at an authenticated gateway so untrusted clients cannot reach the deserializer directly.
- Isolate services that process untrusted Thrift input into resource-constrained containers with CPU and memory limits to contain exhaustion.
# Configuration example: enforce container-level resource limits
# and ingress request size caps while rolling out the 0.25.0 upgrade.
docker run \
--cpus="1.0" \
--memory="512m" \
--memory-swap="512m" \
--pids-limit=256 \
my-thrift-service:patched-0.25.0
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

