# CVE-2026-107908: Pre-authentication heap out-of-bounds write in FalkorDB Bolt BoltReadHandler via RESET message

> Remote unauthenticated attackers can cause denial of service or execute code via heap overflow in FalkorDB's Bolt protocol when enabled.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-jpx9-94mp-7xhq

## What is CVE-2026-107908?

CVE-2026-107908 is a critical memory corruption vulnerability in FalkorDB, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-787 (Out-of-bounds Write)

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


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

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

## Is CVE-2026-107908 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-107908 is a critical memory corruption vulnerability in FalkorDB, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107908 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-107908/ (Markdown: https://insights.sbomify.com/CVE-2026-107908/index.md)
```

## Sources

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

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