Skip to main content

FalkorDB EUVDEUVD-2026-95488

| CVE-2026-107911 HIGH
Access of Resource Using Incompatible Type (Type Confusion) (CWE-843)
2026-10-09 securin GHSA-g4x7-54hf-p7f3
7.7
CVSS 4.0 · Vendor: securin
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate to FalkorDB with GRAPH.QUERY access
  2. Delivery
    Send GRAPH.QUERY with --bolt and crafted argument
  3. Exploit
    Trigger type confusion casting Redis string to Bolt client
  4. Execution
    Result-set code dereferences attacker-influenced pointers
  5. Impact
    Crash server or corrupt/disclose memory

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Type safety enforcement
MITRE ATT&CK

1 technique across 1 tactic: Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated client with permission to execute GRAPH.QUERY (PR:L); the attacker supplies the --bolt argument followed by a crafted Redis string object that FalkorDB casts to a bolt_client_t structure without validating its origin. Critically, this argument is parsed even when the Bolt protocol endpoint is disabled, so no special non-default configuration is needed - default FalkorDB installations before 4.20.0 are affected. Limiting factors: valid authentication and query-execution privileges are required, and high attack complexity (AC:H) means achieving reliable memory disclosure or corruption depends on heap/object layout; a denial-of-service crash is the most readily achievable impact.

Impact

This is a moderate-priority issue rather than an emergency. The vendor-supplied CVSS 4.0 vector (AV:N/AC:H/AT:N/PR:L/UI:N, VC:H/VI:H/VA:H, score 7.7) describes a network-reachable but authentication-gated and high-complexity flaw. PR:L confirms an authenticated attacker is required - specifically a client already permitted to run GRAPH.QUERY - which materially narrows the threat population to users with existing query access. AC:H reflects that reliable memory disclosure or corruption via type confusion requires favorable heap/object layout; denial of service, however, is the realistic and easily achievable outcome, consistent with the 'possibly disclose or corrupt memory' hedge in the description. There is no EPSS score, no CISA KEV listing, and no public exploit referenced in the input, so exploitation is not demonstrated in the wild. Signals are internally consistent: a serious memory-safety bug (CWE-843 type confusion) that is nonetheless bounded by the need for authenticated query access and non-trivial exploitation for anything beyond a crash. The one noteworthy amplifier is that the vulnerable --bolt argument is parsed even when the Bolt endpoint is disabled, so the attack surface is present on default configurations rather than only on hardened/opt-in Bolt deployments.

Exploit ScenarioDerived

An authenticated FalkorDB client that is permitted to issue GRAPH.QUERY sends a query carrying the --bolt flag followed by a crafted argument; FalkorDB casts that ordinary Redis string object to a Bolt client structure and later dereferences attacker-influenced pointers, crashing the server (denial of service) or potentially reading/corrupting process memory. Because the flag is parsed regardless of whether the Bolt endpoint is enabled, default deployments are reachable. No public exploit code is identified at time of analysis, and high attack complexity makes reliable memory corruption harder than a straightforward crash.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 09, 2026

Type confusion in FalkorDB versions before 4.20.0 allows an authenticated client that can issue GRAPH.QUERY to crash the server and, depending on heap layout, potentially disclose or corrupt memory. The flaw lives in the _read_flags handler in src/commands/cmd_dispatcher.c, which accepts a --bolt argument from any client and blindly casts the following Redis string object to a bolt_client_t structure without verifying its origin, so result-set code later dereferences attacker-influenced pointers; the argument is parsed even when the Bolt endpoint is disabled, meaning default installations are exposed. Exploitation requires valid credentials with query-execution rights, and because of the high attack complexity (AC:H) a denial-of-service crash is the most reliable outcome, with memory disclosure or corruption being layout-dependent and not guaranteed; no public exploit code has been identified at time of analysis and the vendor has released a fixed version. This is assessed as a moderate-priority issue rather than an emergency.

RemediationAI

Upgrade to FalkorDB 4.20.0 or later, which is the vendor-released fix confirming removal of the vulnerable Bolt type-handling code; the change is captured in PR #2170 (https://github.com/FalkorDB/FalkorDB/pull/2170), commit 0b11a00b34b25c4d4fdfe55f0a35c8a00593bd7d, and the release tag https://github.com/FalkorDB/FalkorDB/releases/tag/v4.20.0. Because the malicious '--bolt' argument is parsed even when the Bolt endpoint is disabled, turning off Bolt is NOT a valid workaround - do not rely on it. If upgrading is delayed, the effective compensating controls are access-oriented: restrict network reachability to the FalkorDB instance (bind to loopback or a private interface, firewall the Redis port) so only trusted hosts can connect, and tighten ACLs so that GRAPH.QUERY execution is limited to the smallest possible set of identities, accepting that this reduces but does not eliminate risk for any account that legitimately needs query rights. Running the service under a least-privileged OS account and enabling ASLR/heap hardening raises the difficulty of turning the type confusion into reliable memory disclosure or corruption, but the crash/denial-of-service impact remains reachable regardless, so treat these as temporary risk reduction rather than a fix and monitor the vendor advisory for any backported patch for older branches.

Affected VersionsENISA

FalkorDB 0 <4.20.0

Affected Packages

euvd falkordb fix: 4.20.0

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The root cause is a CWE-843 type confusion. FalkorDB is a Redis-module graph database that historically shipped a Bolt protocol endpoint implemented in src/bolt/bolt.c, with the underlying serialization routines built around a bolt_client_t structure containing read/write buffer state. The command dispatcher's _read_flags function parses the optional '--bolt' switch supplied by a client, then treats the subsequent argument - a Redis string object (robj) - as though it were a bolt_client_t pointer, with no type, ownership, or origin check. Downstream result-set code dereferences pointers read from that object, so the address arithmetic depends on the contents and layout of the supplied string rather than on a genuine Bolt client allocation. Because this parse path executes unconditionally during command flag handling, it fires even on configurations where the Bolt listener is turned off, which removes the usual 'non-default configuration required' mitigation and broadens the affected population to essentially every FalkorDB deployment before 4.20.0. The identified fix (PR #2170, commit 0b11a00) removes the entire src/bolt/bolt.c implementation (598 lines of marker-based serialization code), indicating the maintainers eliminated the conflicting type/parsing surface rather than attempting to add a runtime check to the cast.

Know when Redis gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (securin) PRIMARY 7.7 HIGH
CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
vuln.today AI 7.5 HIGH

Network-reachable via GRAPH.QUERY (AV:N) but requires authenticated query access (PR:L) and favorable memory layout for corruption/disclosure (AC:H); no scope change, full CIA impact possible.

3.1 AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (securin).

CVSS VectorVendor: securin

Attack Vector
Network
Attack Complexity
High
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
High
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

DescriptionCVE.org

A type confusion vulnerability in the _read_flags function (src/commands/cmd_dispatcher.c) in FalkorDB before 4.20.0 allows a remote authenticated attacker who can run GRAPH.QUERY to cause a denial of service and possibly disclose or corrupt memory. The function accepts a --bolt argument from any client and casts the following command argument, a Redis string object, to a Bolt client structure without checking its origin; the result-set code then dereferences pointers read from that object. The argument is parsed even when the Bolt endpoint is disabled, so default configurations are affected.

Executive ViewAI

Why It Matters

FalkorDB versions before 4.20.0 contain a high-severity type-confusion flaw that requires valid credentials with query-execution rights and can crash the database server, with layout-dependent potential for memory disclosure or corruption. Default installations are exposed because the vulnerable argument is parsed even when the Bolt endpoint is disabled, so any organization running FalkorDB for production graph workloads should treat availability and data integrity as at risk. No public exploit identified at time of analysis, and Vendor-released patch: 4.20.0 is available.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 73% exploitable
Prevalence
Low
niche graph-database module, limited production footprint versus mainstream datastores
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

38
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +38
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

More in Redis

View all
CVE-2026-48172 CRITICAL POC
10.0 May 21

Privilege escalation to root in the LiteSpeed User-End cPanel Plugin (versions 2.3 through before 2.4.5) lets attackers

CVE-2025-49844 CRITICAL POC
9.9 Oct 03

UAF in Redis 8.2.1 via crafted Lua scripts by authenticated users. EPSS 12.4%. Patch available.

CVE-2022-0543 CRITICAL POC
10.0 Feb 18

It was discovered, that redis, a persistent key-value database, due to a packaging issue, is prone to a (Debian-specific

CVE-2018-11218 CRITICAL POC
9.8 Jun 17

Memory Corruption was discovered in the cmsgpack library in the Lua subsystem in Redis before 3.2.12, 4.x before 4.0.10,

CVE-2025-46817 HIGH POC
7.0 Oct 03

Redis is an open source, in-memory database that persists on disk. Versions 8.2.1 and below allow an authenticated user

CVE-2015-4335 CRITICAL POC
10.0 Jun 09

Redis before 2.8.21 and 3.x before 3.0.2 allows remote attackers to execute arbitrary Lua bytecode via the eval command.

CVE-2016-8339 CRITICAL POC
9.8 Oct 28

A buffer overflow in Redis 3.2.x prior to 3.2.4 causes arbitrary code execution when a crafted command is sent. Rated cr

CVE-2026-77602 CRITICAL POC
9.9 Sep 23

Authenticated remote code execution in OpenC3 COSMOS (Ruby gem 'openc3' versions 5.1.0 through 7.2.1) lets any logged-in

CVE-2026-27574 CRITICAL POC
9.9 Feb 21

Code injection in OneUptime monitoring via custom JS monitor using vm module. PoC and patch available.

CVE-2026-84372 CRITICAL POC
9.8 Sep 01

RESP protocol command injection in Predis, the popular PHP client for Redis and Valkey, affects versions 3.0.0-RC1 throu

CVE-2021-31649 CRITICAL POC
9.8 Jun 24

In applications using jfinal 4.9.08 and below, there is a deserialization vulnerability when using redis,may be vulnerab

CVE-2020-11981 CRITICAL POC
9.8 Jul 17

An issue was found in Apache Airflow versions 1.10.10 and below. Rated critical severity (CVSS 9.8), this vulnerability

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy