CVE-2026-107908

LOWCVSS 9.3 · CRITICAL

Signal is active with 1 mentions in latest observed window

Immediate actions

Track advisory updates for patch or workaround availability

Recommended action window: Monitor and triage in normal cycle

NVD description

A heap-based out-of-bounds write in the BoltReadHandler function (src/bolt/bolt_api.c) in FalkorDB before 4.20.0 allows a remote unauthenticated attacker to cause a denial of service and possibly execute arbitrary code by sending a Bolt RESET message with an attacker-chosen chunk size to the Bolt port. The handler checks the size only with ASSERT(), which is compiled out in release builds, then computes a destination pointer from the wire-supplied 16-bit size and moves buffered data up to about 64 KiB backwards past the start of the read buffer. Only deployments that enable the Bolt endpoint (BOLT_PORT, disabled by default) are affected.

Back to dashboard

0.0/ 10 priority

Sources & remediation

Other references

Weakness type (CWE)

CWE-787

Priority

LOW

Exploitation

NONE

PoC

NONE

Patch

NONE

Momentum

NONE

Threat summary

1 mentions across 1 observed day

What's happening

1 total mentions across 1 day

Deep dive

Activity timeline1 mentions / 1d

Full discourse1 post

Upwind Security MDR@UpwindMDR17h
🚨Critical - FalkorDB Memory Corruption Issues (CVE-2026-5759 / CVE-2026-107908) FalkorDB has two critical memory corruption issues caused by ASSERT() checks that are compiled out in release builds. A crafted RDB stream triggers double free + use-after-free in RdbLoadDeletedNodes (CVE-2026-5759), and a Bolt RESET message with attacker-chosen chunk size causes heap OOB write in BoltReadHandler (CVE-2026-107908). Both allow remote unauthenticated DoS and potentially RCE. Deployments with Bolt disabled (BOLT_PORT unset, default) are not affected by the Bolt issue. 👉Affected: FalkorDB < 4.20.0 | Upgrade to 4.20.0
0000029
315 followersView on X

Explore more

Back to dashboard