Quick answers
- Is CVE-2026-88407 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88407 being exploited in the wild.
- How severe is CVE-2026-88407?
- High severity, with a CVSS score of 7.5, published 21 September 2026.
- Which products and versions are affected?
- FalkorDB v4.20.1 to v4.20.4.
- Is there a fix for CVE-2026-88407?
- 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-88407 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-88407?
- 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 BulkInsert() function parses node_token_count and relation_token_count parameters from command arguments and uses them as loop bounds to iterate over argv[] without first validating that argc contains sufficient elements, leading to an out-of-bounds memory read. The vulnerability occurs in the _BulkInsert_ValidateTokens calls which dereference argv entries beyond the actual argument count, triggering a SIGSEGV. The existing ASSERT checks that should catch this occur after the vulnerable code and are disabled in release builds, providing no protection.
Affected products
- FalkorDB FalkorDB v4.20.1 to v4.20.4
Timeline
- 2026-09-21: disclosed: Advisory published
- 2026-08-05: other: Reported to security@falkordb.com