# CVE-2026-75850: ArcadeDB before 26.8.1 Per-Type ACL Bypass via Batch Handlers

> Attackers with limited permissions can bypass per-type ACLs to read and write unauthorized data via batch handlers in ArcadeDB.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/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:** 19 Aug 2026
- **Also known as:** GHSA-4h2x-5rvm-qq8v, GHSA-c23x-pqcj-7hfm

## What is CVE-2026-75850?

CVE-2026-75850 is a low-severity missing authorization 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 fails to bind the authenticated principal (setCurrentUser) on its batch and time-series HTTP handlers. Because no principal is bound on the worker thread, the engine's fine-grained per-type ACL layer (LocalBucket.checkPermissionsOnFile) does not execute for these handlers. In deployments that use per-type or per-group ACLs, a user with database access but only limited per-type permissions can read from and write to types they are not authorized to access by submitting requests to the batch/time-series endpoints. Deployments that rely solely on database-level access control are not affected.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-75850 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75850 is a low-severity missing authorization 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: There is no known exploitation of CVE-2026-75850 in the wild and no public exploit code.

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

## Sources

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

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