# CVE-2026-75841: ArcadeDB before 26.8.1 Denial of Service via range()

> Authenticated attackers can cause denial of service in ArcadeDB by submitting oversized range() expressions that exhaust server memory.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/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:** 18 Aug 2026
- **Updated:** 18 Aug 2026
- **Also known as:** GHSA-5p5p-rm2x-6rvc, GHSA-xmjm-8q85-g778

## What is CVE-2026-75841?

CVE-2026-75841 is a medium-severity denial of service vulnerability in ArcadeData arcadedb, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ArcadeDB before 26.8.1 contains a denial of service vulnerability in the Cypher range() function that allows authenticated users to exhaust server heap memory. Attackers can submit oversized range() expressions with large bounds to trigger OutOfMemoryError and cause temporary service degradation or unavailability.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling)

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


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

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

## Is CVE-2026-75841 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75841 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75841 is a medium-severity denial of service vulnerability in ArcadeData arcadedb, published on 18 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75841 exists.

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

## Sources

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

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