# CVE-2026-93596: ArcadeDB before 26.9.1 Authorization Bypass via Batch Edge Connect

> Authenticated low-privilege users can bypass ACLs to modify protected graph vertices via batch edge requests due to missing principal binding on async worker threads.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/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 Sep 2026
- **Updated:** 18 Sep 2026
- **Also known as:** GHSA-27vw-j8qc-5h7x, GHSA-frwj-8cg6-5jfh

## What is CVE-2026-93596?

CVE-2026-93596 is a medium-severity missing authorization vulnerability in ArcadeData arcadedb, published on 18 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ArcadeDB before 26.9.1 (com.arcadedb:arcadedb-engine <= 26.8.1) fails to bind the authenticated principal onto the DatabaseAsyncTransaction async worker threads used by the parallel edge-connect phase of POST /api/v1/batch/{database}. Because those workers have no current user, LocalDatabase.checkPermissionsOnFile returns early and allows the write, bypassing per-type CREATE_RECORD/UPDATE_RECORD ACL enforcement. In deployments that rely on per-type or per-group ACLs, an authenticated low-privilege user holding CREATE_RECORD on an edge type E but with CREATE_RECORD/UPDATE_RECORD revoked on a vertex type V can submit a graph edge-load batch request (with parallelFlush at its default value of true) and durably append edges to protected vertices of type V by writing records into V's <V>_out_edges/<V>_in_edges buckets, resulting in unauthorized modification of graph adjacency. Setting parallelFlush=false causes the request to be correctly rejected. This is an incomplete fix of GHSA-c23x-pqcj-7hfm, which bound the principal only on the HTTP handler thread.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-93596 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93596 is a medium-severity missing authorization vulnerability in ArcadeData arcadedb, published on 18 Sep 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-93596 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-93596/ (Markdown: https://insights.sbomify.com/CVE-2026-93596/index.md)
```

## Sources

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

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