ArcadeDB before 26.9.1 Authorization Bypass via Batch Edge Connect (CVE-2026-93596) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-93596

ArcadeDB before 26.9.1 Authorization Bypass via Batch Edge Connect

Answer in brief

CVE-2026-93596 records a Unknown severity vulnerability in ArcadeDB before 26.9.1 Authorization Bypass via Batch Edge Connect. The current sources do not mark it as known exploited. The current feed maps ArcadeData/arcadedb (generic). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 18, 2026Updated Sep 18, 2026Source checked Sep 18, 2026First seen by HOL Sep 18, 2026Material review Sep 18, 2026

Upstream Advisory

Key facts

Risk: Unknown severitySource severity not reported
Exploitation: Not marked as known exploited
Affected software: 1 mapped package or product
Fix availability: Available

Why this deserves its current priority

A CVSS score is not reported in the current record. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps ArcadeData/arcadedb (generic). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
ArcadeData/arcadedbgeneric	>=0 <26.9.1	26.9.1

Recommended response

Check inventory. Check lockfiles and deployed manifests for ArcadeData/arcadedb.
Review the reported fix. Update ArcadeData/arcadedb to 26.9.1 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 18, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 18, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 18, 2026

Sources and claim methodology

Upstream source 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.

Quoted source text, attributed separately from HOL analysis.