CVE-2026-88406

7.5

FalkorDB · FalkorDB (Redis module)

FalkorDB versions 4.20.1 through 4.20.4 contain a stack overflow vulnerability in the _ValidateUnion_Clauses function that allows remote, unauthenticated attackers to cause a Denial of Service.

Executive summary

A stack overflow vulnerability in the FalkorDB Redis module allows unauthenticated remote attackers to trigger a Denial of Service condition.

Vulnerability

The vulnerability is a stack overflow located within the _ValidateUnion_Clauses function in the /ast/ast_validations.c source file. An unauthenticated attacker can trigger this flaw by sending a specifically crafted input to the affected module.

Business impact

The successful exploitation of this vulnerability results in a Denial of Service, which can render the database module unresponsive and disrupt dependent applications. Given the CVSS score of 7.5, this high-severity flaw poses a significant risk to service availability, particularly for production environments relying on FalkorDB for real-time data processing.

Remediation

Immediate Action: Monitor the official FalkorDB GitHub repository for the release of a security patch and apply it as soon as it becomes available.

Proactive Monitoring: Review application logs and Redis module telemetry for abnormal crashes or memory usage spikes that may indicate attempts to trigger the stack overflow.

Compensating Controls: Ensure that access to the Redis instance is restricted via network-level controls, such as firewalls or VPC security groups, to limit the exposure of the module to untrusted traffic.

Exploitation status

Public Exploit Available: No (exploit_available: false)

Analyst recommendation

This vulnerability presents a clear risk to service uptime. Administrators should prioritize identifying instances of FalkorDB running the affected versions and implement strict network access controls immediately. Once the vendor releases the necessary security update, it should be deployed as part of an emergency maintenance cycle to ensure system stability.

More FalkorDB CVEs

History

  1. Disclosed CVE record published
  2. Collected by CVE Brief via github
  3. Analyst report written
  4. Published in the daily brief high section

Sources