Vulnerability  ·  2026-11-22

ArcadeDB MCP upsert tools create types despite allowSchemaChange=false (permission-model bypass)

VulnerabilityLow impactGlobalCVE-2026-134324
The MCP permission model has a distinct allowSchemaChange flag that ExecuteCommandTool respects, but the two upsert tools do not. A UPSERT creating a new type slips past the flag, letting an agent exceed the schema-change boundary the operator configured.
An agent explicitly denied schema change can create types through upsert tools, breaking an operator's intended MCP permission boundary and leaving the schema modified.
The two MCP upsert tools build a Cypher MERGE and run it without gating on the MCP allowSchemaChange flag. A MERGE that names a type which does not exist analyzes as {CREATE, UPDATE} rather than a schema change, so a caller holding insert/update but explicitly denied schema change can create arbitrary new types.
ArcadeDB 26.3.1 before 26.11.1 (MCP upsert_entity / upsert_relationship tools)
Upgrade to ArcadeDB 26.11.1; advisory GHSA-6jr9-6vw5-xjf6 (also tracked with GHSA-r946-225c-5x88 / CVE group).
ArcadeDB GitHub advisory GHSA-6jr9-6vw5-xjf6NVD CVE-2026-134324
See this in the live feed Explore related AI security and governance findings — updated every morning.
Open the feed →