Quick answers
- Is CVE-2026-107911 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-107911 being exploited in the wild.
- How severe is CVE-2026-107911?
- High severity, with a CVSS score of 7.5, published 9 October 2026.
- Which products and versions are affected?
- FalkorDB before 4.20.0.
- Is there a fix for CVE-2026-107911?
- Yes: fixed in FalkorDB 4.20.0. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-107911 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-107911?
- 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.20.0
Technical details
A type confusion vulnerability in the _read_flags function (src/commands/cmd_dispatcher.c) casts a Redis string object to a Bolt client structure without validation, allowing an authenticated attacker to dereference attacker-controlled pointers. The vulnerable code path is reachable via GRAPH.QUERY with a --bolt argument even when the Bolt endpoint is disabled, leading to denial of service, memory disclosure, or memory corruption.
Affected products
- FalkorDB FalkorDB before 4.20.0
Timeline
- 2026-10-09: disclosed