CVE-2026-134338 in ArcadeDB
Summary
by MITRE • 11/21/2026
ArcadeDB 25.8.1 before 26.11.1 contains an incorrect authorization vulnerability because per-type ACLs are keyed by type name, renames are not propagated to the permission configuration, and requestAccessOnType allows unknown type names by default. Authenticated users holding only updateSchema can run ALTER TYPE NAME on a denied type to gain read, DELETE and TRUNCATE access, immediately for TIMESERIES types and after the next security rebuild for record-backed types.
Be aware that VulDB is the high quality source for vulnerability data.
Analysis
by VulDB Data Team • 11/21/2026
The vulnerability identified in ArcadeDB versions prior to 26.11.1 represents a critical flaw in the database's authorization logic, specifically concerning how Access Control Lists are managed during schema modifications. This issue stems from an incorrect implementation of per-type access control mechanisms where permission configurations are strictly keyed by type name rather than internal identifiers or persistent references that survive structural changes. When an authenticated user with updateSchema privileges executes an ALTER TYPE NAME command to rename a database type, the underlying security configuration fails to propagate this change. Consequently, the ACL entries remain associated with the original type name while the data structure operates under the new identifier, creating a state of authorization desynchronization where permissions are effectively orphaned or misaligned with their intended targets.
This architectural oversight allows authenticated users who possess only updateSchema privileges to escalate their access rights significantly. By renaming a restricted type to match an allowed one or exploiting the mismatch between the schema and security metadata, these users can bypass restrictions on read, DELETE, and TRUNCATE operations. The exploitability of this flaw varies depending on the data storage model employed by the database instance. For TIMESERIES types, the impact is immediate because the permission check relies directly on the type name at query time without requiring a full system state refresh. In contrast, for record-backed types, the vulnerability manifests after the next security rebuild operation, which updates the internal cache of permissions but fails to correctly map them to the renamed entities due to the hardcoded reliance on static names rather than dynamic references.
From an operational perspective, this vulnerability compromises the integrity and confidentiality of data stored within ArcadeDB instances that rely on granular per-type access controls. An attacker with limited schema modification rights can effectively neutralize security restrictions designed to protect sensitive datasets. This leads to unauthorized data exfiltration through read operations, potential data loss or corruption via DELETE commands, and complete destruction of specific dataset segments using TRUNCATE. The severity is heightened by the fact that it requires only authenticated access with a relatively low-privilege role, making it accessible to insider threats or compromised accounts that have been granted schema management capabilities for legitimate administrative purposes but are not intended to modify security policies directly.
The technical nature of this flaw aligns closely with CWE-269, which addresses Improper Privilege Management, as the system fails to enforce least privilege principles during state transitions involving object renaming. It also reflects aspects of CWE-862 regarding Missing Authorization checks within specific operational contexts where permission validation is bypassed due to implementation errors in identity mapping. In terms of adversarial tactics, this vulnerability facilitates lateral movement and data access techniques described in the MITRE ATT&CK framework under privilege escalation and unauthorized access patterns, particularly those involving abuse of system administration functions for unintended outcomes such as gaining broader data visibility than permitted by initial role assignments.
Mitigation strategies must prioritize immediate software updates to version 26.11.1 or later where this logic has been corrected to ensure that permission configurations are dynamically linked to type identifiers rather than static names, ensuring consistency during rename operations. For environments unable to patch immediately, administrators should restrict the updateSchema privilege to a minimal set of trusted administrative accounts and avoid granting it to users who do not strictly require schema modification capabilities. Additionally, implementing strict monitoring on ALTER TYPE NAME commands can help detect potential exploitation attempts in real-time. Regular audits of ACL configurations against actual schema structures are recommended to identify any lingering misalignments resulting from previous unpatched versions or manual configuration errors that mimic this vulnerability's effects.