Tabularis interpolated the table_name argument into SQLite PRAGMA metadata queries that its SQL driver could execute as stacked statements. The tool caller needed access to describe_table; the user-facing workflow might have disallowed the separate write-capable run_query tool. Crafted metadata arguments could cross the nominal read-only MCP tool policy…
Inspect the ClaimsCase · DiggingBeagle record
Tabularis MCP read-only metadata tool could execute stacked SQLite statements
Tabularis interpolated the table_name argument into SQLite PRAGMA metadata queries that its SQL driver could execute as stacked statements. Crafted metadata arguments could cross the nominal read-only MCP tool policy and issue statements through the same database connection.
The tool caller needed access to describe_table; the user-facing workflow might have disallowed the separate write-capable run_query tool. The advisory provides SQLite-driver evidence, not confirmation that a compiled vulnerable production binary was exploited.
Assessment profile
Assessment method- Setting
- research demonstration
- Exploitation
- demonstrated
- Evidence
- Grade B
- Remediation
- patch available
- AI role
- AGAINST AI
Basis and provenance
The cited primary technical report or advisory supports the stated mechanism within its reported scope. The assessment does not infer a production breach, a victim count or a comparable impact score from a laboratory result. A maintainer or advisory names a patched release; that does not prove every deployed instance has updated. Boundary: The supposed read-only boundary covered one MCP tool name, but describe_table assembled SQL from a caller-controlled table identifier.
Assessed Oct 29, 2026 using diggingbeagle.assessment/1.
Evidence basis: CLM-CP23-TABULARIS-MCP-METADATA-SQL-1 · CLM-ENRICH-20261029-32 · Tabularis SQLite MCP describe_table command SQL injection advisory
At a glance
Crafted metadata arguments could cross the nominal read-only MCP tool policy and issue statements through the same database connection.
Read the implicationsThe advisory provides SQLite-driver evidence, not confirmation that a compiled vulnerable production binary was exploited.
Limits and uncertaintyFull account
Tabularis interpolated the table_name argument into SQLite PRAGMA metadata queries that its SQL driver could execute as stacked statements.
The tool caller needed access to describe_table; the user-facing workflow might have disallowed the separate write-capable run_query tool. Crafted metadata arguments could cross the nominal read-only MCP tool policy and issue statements through the same database connection.
The advisory provides SQLite-driver evidence, not confirmation that a compiled vulnerable production binary was exploited. Use Tabularis 0.28.0 or newer, strictly validate identifiers and apply SQLite read-only connection permissions when writes are not authorized.
Evidence interpretation and control boundary. The supposed read-only boundary covered one MCP tool name, but describe_table assembled SQL from a caller-controlled table identifier. Where the SQLite driver accepts stacked statements, the same metadata operation can perform writes with the configured database authority. The advisory includes a lower-level SQLite proof and does not establish that an attacker compromised a deployed Tabularis instance.
Mechanism and trust boundary
- 01
Step
- 02
Step
- 03
Step
Claims & evidence
CLM-ENRICH-20261029-32The Tabularis advisory reports SQL interpolation in describe_table metadata queries that may allow stacked statements through a nominal read-only MCP tool under the database connection privileges.supported
Basis: reported finding
- supportsTabularis SQLite MCP describe_table command SQL injection advisoryprimary disclosure
GHSA-xrx3-j98v-67x9: describe_table PRAGMA, stacked SQL and 0.28.0 fix
CLM-CP23-TABULARIS-MCP-METADATA-SQL-1Tabularis interpolated the table_name argument into SQLite PRAGMA metadata queries that its SQL driver could execute as stacked statements. The tool caller needed access to describe_table; the user-facing workflow might have disallowed the separate write-capable run_query tool. Crafted metadata arguments could cross the nominal read-only MCP tool policy and issue statements through the same database connection.supported
Basis: reported finding
- supportsTabularis SQLite MCP describe_table command SQL injection advisoryprimary disclosure
GHSA-xrx3-j98v-67x9: describe_table PRAGMA, stacked SQL and 0.28.0 fix
Implications
Crafted metadata arguments could cross the nominal read-only MCP tool policy and issue statements through the same database connection.
Controls and mitigations
- Use Tabularis 0.28.0 or newer, strictly validate identifiers and apply SQLite read-only connection permissions when writes are not authorized.
Unknowns and contradictions
- The advisory provides SQLite-driver evidence, not confirmation that a compiled vulnerable production binary was exploited.
Sources and citation
Material revision history
- Oct 29, 2026 · Canonical change recorded · new in release · revision 202