# CVE-2026-88412: FalkorDB integer overflow in bulk insert array parsing

Source: https://junglewise.ai/threats/cve-2026-88412-an-integer-overflow-in-the-bulkinsert-readproperty-component-bulk  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-21. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-88412 · Severity: medium · CVSS 5.3 · Published 2026-09-21

FalkorDB is a graph database module for Redis that supports bulk insert operations. An integer overflow vulnerability in array parsing allows an authenticated attacker to trigger excessive memory allocation, causing the database to consume tens of gigabytes of RAM and crash, disrupting service availability.

Technologies: [FalkorDB](https://junglewise.ai/threats/technologies/falkordb). Vendors: [FalkorDB](https://junglewise.ai/threats/vendors/falkordb).

## 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

## References

- [https://github.com/FalkorDB/FalkorDB/issues/2326](https://github.com/FalkorDB/FalkorDB/issues/2326)

## Related threats

- [FalkorDB type confusion in _read_flags function](https://junglewise.ai/threats/cve-2026-107911-a-type-confusion-vulnerability-in-the-read-flags-function-src)
- [FalkorDB improper authentication in Bolt endpoint](https://junglewise.ai/threats/cve-2026-107910-an-improper-authentication-vulnerability-in-the-is-authenticated)
- [FalkorDB heap-based buffer overflow in WebSocket frame handling](https://junglewise.ai/threats/cve-2026-107909-a-heap-based-out-of-bounds-write-in-the-ws-read-frame-function)
- [FalkorDB heap-based buffer overflow in Bolt handler](https://junglewise.ai/threats/cve-2026-107908-a-heap-based-out-of-bounds-write-in-the-boltreadhandler-function)
- [FalkorDB stack-based buffer overflow in RDB graph entity decoder](https://junglewise.ai/threats/cve-2026-7827-a-stack-based-buffer-overflow-in-the-rdbloadentity-function-of-the)