What happened
The read-only classification walks the SQL AST with Class.getDeclaredFields(); without GraalVM reflection metadata the native binary sees an empty AST and answers 'complete'/idempotent. Statements holding writes inside a SELECT are therefore classified as READ and executed by read-only doors, including the MCP read-only mode an operator may rely on to stop an AI agent from writing.
Why it matters
An operator constrains an agent via MCP read-only mode to prevent writes; this classification failure lets the agent write durably through the very path meant to be non-mutating.
Attack vector
In native-image builds, missing reflection metadata leaves SqlAstInspector with an empty AST, so writes nested inside a SELECT (projection subquery or LET clause) are misclassified as idempotent/READ. This lets an authenticated client persist writes through paths meant to be read-only — POST /api/v1/query, the MCP read-only mode (ExecuteCommandTool/QueryTool/SampleRecordsTool), and HA leader-routing checks.
Affected systems
ArcadeDB native-image server builds 26.8.1 before 26.11.1 (JVM build is not affected)
Mitigation
Upgrade to ArcadeDB 26.11.1. Advisory GHSA-84m7-76gh-rm42.