Skip to content

CVE-2026-107908: FalkorDB Pre-Auth Remote Code Execution via Bolt Protocol Assertion Bypass

Density:
C-Level Executive Briefing CVE-2026-107908 CRITICAL SCORE 96/100

Critical pre-auth heap out-of-bounds write in FalkorDB GraphRAG memory engine. Release builds strip assertion validation, enabling arbitrary command execution.

HERMES

HERMES THREAT SCORE & GRAPHRAG VECTOR STORE EVALUATION

Target: FalkorDB Graph Engine โ€” Bolt Network Daemon (BoltReadHandler)
Confidence: 98%
96 / 100
CRITICAL

Measures real-world operational relevance, exploit weaponization, and active threat posture.

Dimension Breakdown
Exploitability 20 / 20
Threat Activity 18 / 20
Weaponization 19 / 20
Exposure 19 / 20
Prevalence 18 / 20
Impact 20 / 20
Exploit Maturity 19 / 20
Attack Chain Potential 20 / 20
โš–๏ธ Divergence & Operational Rationale

Both CVSS v3.1 (9.8 Critical) and Hermes Threat Score (96) recognize the catastrophic severity of this flaw. FalkorDB is widely deployed as the low-latency Knowledge Graph memory backend for LLM multi-agent systems and GraphRAG architectures. The reliance on disabled-in-production assertions allows network-level unauthenticated heap corruption directly into GraphRAG memory spaces, yielding instant subversion of AI context stores and host compromise.

๐Ÿ•ธ๏ธ Connected Knowledge Graph & Provenance

CVE-2026-107908: FalkorDB Pre-Auth Remote Code Execution via Bolt Protocol Assertion BypassVULNERABILITY

Connected Nodes: 1
Active Relationships (Outgoing)
→ affectsPRODUCTFalkorDB Graph Database Engine
98% VERY_HIGH

Software platform affected by security vulnerabilities and agentic attack patterns.

๐Ÿ” Why is this related? (Evidence & Provenance)

“Confirmed security vulnerability in FalkorDB Graph Database Engine documented in Hermes dossier.”

Supporting Verified Evidence:

FalkorDB integrates a native implementation of Neo4jโ€™s binary Bolt protocol (src/bolt/bolt_api.c) to serve ultra-low-latency graph queries. When ingesting framed Bolt binary streams, BoltReadHandler handles chunk reassembly.

The vulnerability stems from relying upon the standard ASSERT() macro to validate incoming stream offsets:

// Vulnerable logic in src/bolt/bolt_api.c (Prior to 4.20.0)
int BoltReadHandler(client_connection *conn) {
uint16_t chunk_size = read_uint16(conn->buffer);
// In DEBUG builds, this prevents out-of-bounds indexing.
// In RELEASE (-DNDEBUG) builds, this statement is COMPILED OUT COMPLETELY:
ASSERT(conn->read_offset + chunk_size <= conn->buffer_capacity);
// Attacker sends crafted negative offset or overflow size:
conn->read_offset -= chunk_size;
memcpy(conn->read_buffer + conn->read_offset, conn->stream_data, chunk_size);
return 0;
}

Because production distribution packages are compiled with -O2 -DNDEBUG, the safety assertion evaporates. A remote attacker sending a malformed Bolt RESET message can decrement the buffer cursor below zero, allowing an attacker-controlled heap out-of-bounds overwrite of adjacent socket metadata and function dispatch tables.


When FalkorDB is deployed as the context memory for LLM reasoning agents (GraphRAG):

  1. Context Memory Hijacking: An attacker can overwrite graph relationships, poisoning agent retrieval knowledge.
  2. Host Remote Code Execution: Overwriting the redis/falkordb module command table triggers arbitrary shell commands under the database user context.

title: FalkorDB Bolt Protocol Anomaly - Chunk Size Buffer Rewind
id: falkordb-cve-2026-107908-bolt-rce
status: experimental
description: Detects malformed Bolt protocol frames with negative chunk offsets directed at FalkorDB listeners.
logsource:
category: network_traffic
detection:
selection:
destination_port: 7687 # Default Neo4j/Bolt Port
bolt_magic_header: '6060B017'
bolt_negative_chunk: true
condition: selection
level: critical
tags:
- attack.initial_access
- attack.t1190

  1. Upgrade immediately: Deploy FalkorDB 4.20.0 or later across all container images and orchestration clusters.
  2. Disable Unnecessary Bolt Listeners: If your agents interact strictly via Redis Cypher commands (GRAPH.QUERY), ensure Bolt is explicitly disabled in falkor.conf.
  3. Perimeter Isolation: Never expose port 7687 or FalkorDB listeners to untrusted public networks; isolate within internal VPC subnets.