Memory exhaustion via reported RESP aggregate allocation
Published Sep 24, 2026 · Updated Sep 24, 2026
Uncontrolled memory allocation in the hiredis RESP aggregate parser at commit 29ea279 allows attackers to exhaust client-process memory. The advisory attributes the flaw to aggregate parsing, but the cited public commit changes only TLS error handling and a reconnect test, not RESP allocation logic. Public evidence therefore does not establish the malformed input, reachable attack path, affected version range, or exact interruption mode.
Summary
What happened
Uncontrolled memory allocation in the hiredis RESP aggregate parser at commit 29ea279 allows attackers to exhaust client-process memory. The advisory attributes the flaw to aggregate parsing, but the cited public commit changes only TLS error handling and a reconnect test, not RESP allocation logic. Public evidence therefore does not establish the malformed input, reachable attack path, affected version range, or exact interruption mode.
The record
- CVE
- CVE-2026-88382
- Published
- Sep 24, 2026
- Updated
- Sep 24, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- Unavailable
- Attack vector
- Unavailable
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 24, 2026CVE publishedPublication date reported by the CVE source.
- Sep 24, 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?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
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
No sourced classifications are available.
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