Authenticated service crash via unbounded query keys
Published Sep 21, 2026 · Updated Sep 21, 2026
Stack exhaustion in FalkorDB 4.20.1 through 4.20.4 allows remote authenticated users to crash the server with a crafted graph query. The _GetGroup() function in src/execution_plan/ops/op_aggregate.c allocates a variable-length stack array from the unbounded number of key expressions in the query's RETURN clause. A connection permitted to run GRAPH.QUERY is required; exhausting the process stack triggers SIGSEGV, terminates the server, and loses non-persisted graph data.
Summary
What happened
Stack exhaustion in FalkorDB 4.20.1 through 4.20.4 allows remote authenticated users to crash the server with a crafted graph query. The _GetGroup() function in src/execution_plan/ops/op_aggregate.c allocates a variable-length stack array from the unbounded number of key expressions in the query's RETURN clause. A connection permitted to run GRAPH.QUERY is required; exhausting the process stack triggers SIGSEGV, terminates the server, and loses non-persisted graph data.
The record
- CVE
- CVE-2026-88408
- Published
- Sep 21, 2026
- Updated
- Sep 21, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- T1499
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 21, 2026CVE publishedPublication date reported by the CVE source.
- Sep 21, 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
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