Quick answers
- Is CVE-2026-88410 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88410 being exploited in the wild.
- How severe is CVE-2026-88410?
- High severity, with a CVSS score of 7.1, published 21 September 2026.
- Which products and versions are affected?
- FalkorDB 4.20.1 to 4.20.4.
- Is there a fix for CVE-2026-88410?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-88410 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-88410?
- Check whether you run FalkorDB at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The graph.UDF command is not registered as a write operation despite mutating persistent state and being written to RDB, bypassing replica write restrictions and deny-oom checks. The RDB decoder uses unchecked ASSERT() statements that compile out in release builds, causing malformed UDF data to be silently skipped; additionally, zero-length string buffers trigger size_t underflow. An authenticated attacker can register a UDF containing an infinite loop to permanently hang a worker thread, as the QuickJS runtime lacks an interrupt handler and timeout mechanism comparable to Redis's SCRIPT KILL.
Affected products
- FalkorDB FalkorDB 4.20.1 to 4.20.4
Timeline
- 2026-09-21: disclosed