CVE-2026-67344: ArcadeDB before 26.7.2 Authentication Bypass via ALTER TYPE
ArcadeDB before 26.7.2 fails to enforce the UPDATESCHEMA database permission on the ALTER TYPE ... CUSTOM and ALTER TYPE ... BUCKETSELECTIONSTRATEGY SQL operations, which map to setCustomValue and setBucketSelectionStrategy in LocalDocumentType. An authenticated user with only read access (e.g., a read-only API token) can submit these ALTER TYPE statements via the HTTP command endpoint to mutate a type's custom schema metadata and bucket-selection strategy, bypassing the documented updateSchema permission boundary and potentially corrupting schema metadata and record routing.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ArcadeDBto a version that resolves this vulnerability.Fixed in 26.7.2 - Compensating control
Restrict access to the HTTP command endpoint so that users/tokens with only read access (e.g., read-only API tokens) cannot send SQL such as ALTER TYPE / BUCKETSELECTIONSTRATEGY.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-67344?
The severity of CVE-2026-67344 is medium with a score of 4.3.
How does CVE-2026-67344 affect ArcadeDB?
CVE-2026-67344 allows an authenticated user with read access to bypass authentication and execute unauthorized ALTER TYPE operations.
What are the affected versions for CVE-2026-67344?
CVE-2026-67344 affects ArcadeDB versions prior to 26.7.2.
How do I fix CVE-2026-67344?
To fix CVE-2026-67344, upgrade ArcadeDB to version 26.7.2 or later.
What type of attacks can CVE-2026-67344 facilitate?
CVE-2026-67344 can facilitate unauthorized changes to database types by exploiting insufficient permission checks.