# CVE-2026-88412: Integer overflow in n/a

> Attackers can cause a Denial of Service in FalkorDB via crafted input triggering an integer overflow in the bulk insert component.

- **Severity:** Medium 5.3 (`CVSS:3.1/AC:L/AV:N/A:L/C:N/I:N/PR:N/S:U/UI:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 21 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-ch94-pjvv-7fwf

## What is CVE-2026-88412?

CVE-2026-88412 is a medium-severity vulnerability in n/a, published on 21 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An integer overflow in the _BulkInsert_ReadProperty component (/bulk_insert.c) of FalkorDB (Redis module) v4.20.1 allows attackers to cause a Denial of Service (DoS) via a crafted input.

Weakness: CWE-190 (Integer Overflow or Wraparound)

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


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

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

## Is CVE-2026-88412 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-88412 is a medium-severity vulnerability in n/a, published on 21 Sep 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-88412 in the wild and no public exploit code.

Affected product: n/a. 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-88412/ (Markdown: https://insights.sbomify.com/CVE-2026-88412/index.md)
```

## Sources

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

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