# CVE-2026-75842: ArcadeDB before 26.8.1 Arbitrary File Read via LOAD CSV

> Authenticated users can read arbitrary local files via the LOAD CSV command, potentially exposing sensitive data.

- **Severity:** High 8.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/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:** 19 Aug 2026
- **Also known as:** GHSA-88hc-8h63-mm6w, GHSA-hfp5-6gcp-8c75

## What is CVE-2026-75842?

CVE-2026-75842 is a high-severity path traversal 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 versions before 26.8.1 contain an arbitrary file read vulnerability in the OpenCypher LOAD CSV FROM clause that allows authenticated users to read local files. Attackers with read query privileges can use the file:// protocol in LOAD CSV statements to access arbitrary files with server process privileges, exfiltrating sensitive data directly in query responses.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

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

## Is CVE-2026-75842 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75842 is a high-severity path traversal 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-75842 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-75842/ (Markdown: https://insights.sbomify.com/CVE-2026-75842/index.md)
```

## Sources

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

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