# CVE-2026-107911: Type confusion in FalkorDB GRAPH.QUERY via the --bolt argument

> Remote authenticated attackers can cause denial of service and potential memory disclosure in FalkorDB via type confusion in GRAPH.QUERY.

- **Severity:** High 7.7 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 9 Oct 2026
- **Also known as:** GHSA-g4x7-54hf-p7f3

## What is CVE-2026-107911?

CVE-2026-107911 is a high-severity memory corruption vulnerability in FalkorDB, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-843 (Access of Resource Using Incompatible Type)

## Which versions are affected by CVE-2026-107911?


## How do I fix CVE-2026-107911?

No fix has been published for CVE-2026-107911 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-107911 being exploited?

There is no known exploitation of CVE-2026-107911 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107911 and fix it if it is affected.

What it is: CVE-2026-107911 is a high-severity memory corruption vulnerability in FalkorDB, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107911 in the wild and no public exploit code.

Affected product: FalkorDB. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-107911/ (Markdown: https://insights.sbomify.com/CVE-2026-107911/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107911
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107911
- OSV: https://osv.dev/vulnerability/CVE-2026-107911

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107911/
Summaries are generated and may contain mistakes; the official description above is the record.