Quick answers
- Is CVE-2026-5759 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-5759 being exploited in the wild.
- How severe is CVE-2026-5759?
- Critical severity, with a CVSS score of 9.8, published 9 October 2026.
- Which products and versions are affected?
- FalkorDB before 4.18.1.
- Is there a fix for CVE-2026-5759?
- Yes: fixed in FalkorDB 4.18.1. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-5759 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-5759?
- 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.
How to fix
- Fixed in: FalkorDB 4.18.1
Technical details
The RdbLoadDeletedNodes function in the RDB graph decoders lacks proper validation of the deleted-nodes buffer length in release builds, relying only on ASSERT() which is compiled out. When a crafted RDB stream has a buffer length not aligned to sizeof(NodeID), the function frees the buffer but then reads and frees it again, causing use-after-free and double-free conditions. An attacker with Redis replication command access can exploit this with a specially crafted RDB stream.
Affected products
- FalkorDB FalkorDB before 4.18.1
Timeline
- 2026-10-09: disclosed