Thanks for helping keep Tabularis and its users safe. We take security reports seriously and appreciate responsible disclosure.

Only the latest released version receives security fixes. Fixes are shipped in a new release rather than backported to older ones, so please upgrade to the most recent version before reporting an issue.

Please do not open a public issue for security problems, and don't disclose the details publicly until a fix has shipped.

Use one of these private channels instead:

1. GitHub private vulnerability reporting (preferred) — go to the Security tab of this repository and click Report a vulnerability. This keeps the report private and lets us collaborate on the advisory and fix in one place.
2. Email — if you'd rather not use GitHub, write to andrea@debbaweb.it with [SECURITY] in the subject.

The more of this you can provide, the faster we can confirm and fix:

• A clear description of the issue and its impact.
• The affected component, file, and (if known) the line or function.
• Steps to reproduce, or a proof of concept.
• The threat model you're assuming (e.g. untrusted MCP input, a malicious connected server, a prompt-injected agent turn, a local operator).
• Any suggested fix or mitigation.

Tabularis is a desktop database client with an MCP layer that lets AI agents run queries against your databases. Reports that are especially in scope include:

• Bypasses of the MCP safety guarantees — read-only mode or the write-approval gate (for example, a statement that executes writes/DDL but is classified as a read).
• SQL that reaches a database in a way the safety layer was expected to block.
• Exposure of stored credentials or connection secrets.
• Any way untrusted input (a connected MCP server, a prompt-injected agent) can perform actions the user did not approve.

Please assume the realistic threat model where the query text reaching Tabularis may come from an untrusted source — that's exactly what the safety layer exists to contain.

• We'll acknowledge your report within 3 business days.
• We'll keep you updated on our progress toward a fix.
• We'll credit you in the release notes and the advisory once the fix ships, unless you prefer to stay anonymous.

Thank you for reporting responsibly.