Quick answers
- Is CVE-2026-88412 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-88412 being exploited in the wild.
- How severe is CVE-2026-88412?
- Medium severity, with a CVSS score of 5.3, published 21 September 2026.
- Which products and versions are affected?
- FalkorDB 4.20.1.
- Is there a fix for CVE-2026-88412?
- 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-88412 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-88412?
- 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_ReadProperty function in bulk_insert.c reads a signed int64_t length from the binary payload without validation before passing it to SIArray_New(), which expects an unsigned uint32_t. A negative length is implicitly converted to a very large unsigned value, causing massive unvalidated allocation. The subsequent population loop never executes because the signed/unsigned comparison fails, resulting in pure memory waste and potential out-of-memory termination on constrained systems.
Affected products
- FalkorDB FalkorDB 4.20.1
Timeline
- 2026-08-05: disclosed
- 2026-09-21: advisory