Unauthenticated memory exhaustion via retained function queues
Published Sep 14, 2026 · Updated Sep 14, 2026
Resource exhaustion in Apache Storm DRPC 3.0.0 allows remote attackers to exhaust server heap via distinct function names. The DRPC server creates a request-queue map entry for every client-supplied function name but never removes the entry after its queue empties. The endpoint requires only network reachability when the default unset authorizer is retained, and its permanent memory growth eventually interrupts service.
Summary
What happened
Resource exhaustion in Apache Storm DRPC 3.0.0 allows remote attackers to exhaust server heap via distinct function names. The DRPC server creates a request-queue map entry for every client-supplied function name but never removes the entry after its queue empties. The endpoint requires only network reachability when the default unset authorizer is retained, and its permanent memory growth eventually interrupts service.
The record
- CVE
- CVE-2026-82439
- Published
- Sep 14, 2026
- Updated
- Sep 14, 2026
- Vendor
- Apache Software Foundation
- Product
- Apache Storm DRPC
- Classifications
- T1499.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 14, 2026CVE publishedPublication date reported by the CVE source.
- Sep 14, 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=3.0.0 <3.1.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.
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
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo