CVE-2026-93595: ArcadeDB before 26.9.1 ACL Bypass via query_database Tool
ArcadeDB before 26.9.1 contains an access control bypass vulnerability in the querydatabase tool exposed through the AI chat endpoints. The tool executes queries without binding the authenticated principal to DatabaseContext, causing per-type and per-bucket ACL checks to silently no-op and allowing authenticated users to read data they are explicitly denied at the per-type level. Attackers can prompt the AI assistant to execute queries against restricted types or buckets to retrieve sensitive data that would be rejected through normal query endpoints.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
ArcadeDBto a version that resolves this vulnerability.Fixed in 26.9.1 - Compensating control
Restrict/disable access to the AI chat endpoints that expose the query_database tool until ArcadeDB is upgraded to 26.9.1, to prevent exploitation of the ACL bypass.
Event History
Frequently Asked Questions
Who can exploit this issue?
An authenticated user who can access the AI chat endpoints can exploit it. The user must be able to prompt the AI assistant to invoke the query_database tool.
What data is exposed?
Data in types or buckets that the authenticated user is explicitly denied through per-type or per-bucket ACLs may be readable. Queries that would be rejected through normal query endpoints can return restricted data through the AI chat query_database tool.
Are normal database query endpoints affected?
The described bypass is specific to the query_database tool exposed through AI chat endpoints. Normal query endpoints are described as rejecting the restricted queries.
Which versions need remediation?
ArcadeDB versions before 26.9.1 are affected. Upgrading to 26.9.1 or later addresses the affected version range.