CVE-2026-119576 in ArcadeDB
Summary
by MITRE • 10/30/2026
ArcadeDB from 21.12.1 before 26.10.2 contains an authorization bypass vulnerability that allows users with only readRecord to replace the shared GraphQL schema via the read-only query endpoint. Attackers can send a GraphQL type definition with a crafted @sql directive to /api/v1/query/{database}, altering query results returned to other users including administrators.
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Analysis
by VulDB Data Team • 10/30/2026
ArcadeDB versions prior to 26.10.2 contain a critical authorization bypass vulnerability that undermines the integrity of the database's shared GraphQL schema through improper access control enforcement on read-only endpoints. The flaw resides in the handling of the /api/v1/query/{database} endpoint, which is intended for executing read operations and should not permit modifications to global configuration or schema definitions. However, due to insufficient validation of user permissions relative to the specific operation being performed, an attacker with only the minimal readRecord privilege can exploit this misconfiguration to inject malicious GraphQL type definitions into the shared schema. This bypass allows a low-privilege user to effectively escalate their capabilities beyond what is permitted by their assigned role, violating the principle of least privilege and compromising the security boundary between different levels of database access.
The technical mechanism of exploitation involves crafting a specific GraphQL query that includes a @sql directive within a type definition payload. When this crafted request is sent to the read-only query endpoint, the server incorrectly processes it as a schema modification command rather than rejecting it due to insufficient permissions. By altering the shared GraphQL schema, an attacker can redefine how data types are interpreted and returned by the database engine. This manipulation allows the injection of custom logic or malformed structures that alter the output format and content of queries executed by other users. Since the schema is shared across all sessions connected to the database, this change affects every user interacting with the system, including administrators who rely on accurate data representation for management tasks and decision-making processes.
The operational impact of this vulnerability is severe as it enables a denial of service through data corruption or potential information disclosure depending on how the altered schema interprets underlying records. Attackers can manipulate query results to return fabricated data, hide sensitive information by altering field mappings, or cause system instability if the injected SQL directives conflict with existing database structures. For administrators, this means that monitoring tools and administrative interfaces relying on GraphQL queries may display incorrect metrics or configurations, leading to misguided remediation efforts or failure to detect other ongoing attacks. The ability to persistently alter the schema without proper authentication checks represents a significant breach of data integrity, as subsequent sessions will inherit these malicious definitions until they are manually reverted by an administrator with sufficient privileges.
This vulnerability aligns with CWE-269 Improper Privilege Management and CWE-77 SQL Injection via GraphQL directives, highlighting failures in both access control logic and input validation for database commands. In the context of the MITRE ATT&CK framework, this behavior corresponds to T1059 Command and Scripting Interpreter through the abuse of legitimate system tools (GraphQL engine) and potentially T1482 Domain Controller Security Software Discovery if used to map out network structures via altered schema responses. To mitigate this risk, organizations must immediately upgrade ArcadeDB to version 26.10.2 or later where these authorization checks have been hardened. Additionally, until an upgrade is feasible, administrators should restrict access to the /api/v1/query/{database} endpoint using firewall rules or reverse proxy configurations that limit connectivity to trusted IP addresses only. Implementing strict input validation on GraphQL schemas and auditing query logs for unusual type definition injections can also help in detecting attempts to exploit this flaw before significant damage occurs.