ArcadeDB before 26.9.1 ACL Bypass via Index and TimeSeries (CVE-2026-93594) | HOL Guard CVE

Unknown severity · Source severity not reportedCVE-2026-93594

ArcadeDB before 26.9.1 ACL Bypass via Index and TimeSeries

Answer in brief

CVE-2026-93594 records a Unknown severity vulnerability in ArcadeDB before 26.9.1 ACL Bypass via Index and TimeSeries. 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 (Maven artifact com.arcadedb:arcadedb-engine) through 26.8.1 enforces its per-type/per-record access-control rules only in LocalBucket, keyed on file id. Query-execution paths that reach record data through LSM index files or the TimeSeries engine never invoke that permission check, so an authenticated user who is denied readRecord/deleteRecord on a type can still, with a single ordinary SQL statement, read the type's indexed key values and record IDs (e.g. SELECT key, rid FROM INDEX:Type[field]), read MAX/MIN values via the index shortcut, read and count TimeSeries samples, learn the type's record count, and delete index entries (DELETE FROM INDEX:Type[field]), which desynchronizes the index from the data and can defeat unique constraints. Index and type names needed for exploitation are discoverable because SELECT FROM schema:indexes is unfiltered. The issue affects both embedded and server deployments and all transports (HTTP, Bolt, Postgres, Gremlin) once a principal is bound. Fixed in 26.9.1.

Quoted source text, attributed separately from HOL analysis.