Service interruption via leaked HTTP request contexts
Published Oct 2, 2026 · Updated Oct 2, 2026
Memory leakage in Apache Thrift C++ TEvhttpServer before 0.25.0 allows remote attackers to exhaust server memory via malformed HTTP requests. Its process method allocates a RequestContext but leaves it owned by the completion callback, which is never reached when the processor throws before calling back. A deployment must expose the libevent-backed C++ HTTP server; repeated requests can consume memory until the service is interrupted.
Summary
What happened
Memory leakage in Apache Thrift C++ TEvhttpServer before 0.25.0 allows remote attackers to exhaust server memory via malformed HTTP requests. Its process method allocates a RequestContext but leaves it owned by the completion callback, which is never reached when the processor throws before calling back. A deployment must expose the libevent-backed C++ HTTP server; repeated requests can consume memory until the service is interrupted.
The record
- CVE
- CVE-2026-94652
- Published
- Oct 2, 2026
- Updated
- Oct 2, 2026
- Vendor
- The Apache Software Foundation
- Product
- Apache Thrift
- Classifications
- T1499.004
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Oct 2, 2026CVE publishedPublication date reported by the CVE source.
- Oct 2, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <0.25.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Activity data is delayed. The latest report is Sep 28, 2026.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started