# CVE-2026-7827: Stack-based buffer overflow in FalkorDB _RdbLoadEntity via unbounded property count in crafted RDB

> Remote attackers can cause denial of service or execute arbitrary code via crafted RDB streams in FalkorDB graph decoders.

- **Severity:** Critical 9.2 (`CVSS:4.0/AV:N/AC:H/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:** 9 Oct 2026
- **Also known as:** GHSA-fwp9-2ghh-pw8g

## What is CVE-2026-7827?

CVE-2026-7827 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 stack-based buffer overflow in the _RdbLoadEntity function of the RDB graph decoders (src/serializers/decoders/*/decode_graph_entities.c) in FalkorDB before 4.18.4 allows a remote attacker who can issue Redis replication commands (for example, against an instance with no password configured) to cause a denial of service and possibly execute arbitrary code by supplying a crafted RDB stream with an attacker-controlled entity property count. The count sizes two variable-length arrays on the thread stack with no upper bound, and the decoder then fills them with attacker-supplied values.

Weakness: CWE-121 (Stack-based Buffer Overflow)

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


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

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

## Is CVE-2026-7827 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-7827 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-7827 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-7827/ (Markdown: https://insights.sbomify.com/CVE-2026-7827/index.md)
```

## Sources

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

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