Quick answers
- Is CVE-2026-7827 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-7827 being exploited in the wild.
- How severe is CVE-2026-7827?
- High severity, with a CVSS score of 8.1, published 9 October 2026.
- Which products and versions are affected?
- FalkorDB before 4.18.4.
- Is there a fix for CVE-2026-7827?
- 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-7827 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-7827?
- 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 stack-based buffer overflow exists in the _RdbLoadEntity function within RDB graph decoders (src/serializers/decoders/*/decode_graph_entities.c), where variable-length arrays are sized on the thread stack using an attacker-controlled property count from the RDB stream with no upper bounds. An attacker with access to Redis replication commands can supply a crafted RDB stream to exhaust stack memory and trigger code execution or denial of service. The fix replaces VLA allocations with bounded heap allocations and adds UINT16_MAX checks.
Affected products
- FalkorDB FalkorDB before 4.18.4
Timeline
- 2026-10-09: disclosed
- 2026-05-07: patched