Quick answers
- Is CVE-2026-7826 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-7826 being exploited in the wild.
- How severe is CVE-2026-7826?
- Critical severity, with a CVSS score of 9.1, published 9 October 2026.
- Which products and versions are affected?
- FalkorDB before 4.18.4.
- Is there a fix for CVE-2026-7826?
- Yes: fixed in FalkorDB 4.18.4. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-7826 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-7826?
- 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.4
Technical details
A heap-based out-of-bounds read exists in the BufferSerializerIOv2_ReadBuffer function (src/serializers/serializer_io.c) due to missing runtime bounds checks on the sub-buffer length field when processing RDB streams. The only validation is an ASSERT() macro that is compiled out in release builds, allowing memcpy() to read past heap allocation boundaries. A remote attacker who can send Redis replication commands can exploit this by supplying a crafted RDB stream with a length field exceeding the remaining buffer size, causing memory disclosure or denial of service.
Affected products
- FalkorDB FalkorDB before 4.18.4
Timeline
- 2026-10-09: disclosed