CVE-2026-17351

*** Pendiente de traducción *** The fix for CVE-2026-12045 in pgAdmin 4 9.16 required the LLM-supplied query passed to the AI Assistant&amp;#39;s execute_sql_query tool to parse, via sqlparse, as exactly one non-transaction-control statement before running it inside a BEGIN TRANSACTION READ ONLY wrapper. sqlparse&amp;#39;s string-literal lexing can disagree with PostgreSQL&amp;#39;s own parser: under standard_conforming_strings = on (PostgreSQL&amp;#39;s default since 9.1), a backslash immediately before a quote is an ordinary character to PostgreSQL, but sqlparse treats it as escaping the quote. A payload such as SELECT &amp;#39;\&amp;#39;;COMMIT;CREATE TABLE pwn(x int);SELECT 1 --&amp;#39; therefore parses as a single SELECT to sqlparse&amp;#39;s validator, while PostgreSQL executes it as four statements: the smuggled COMMIT ends the wrapping read-only transaction, and the trailing ROLLBACK becomes a no-op. This reintroduces the same write/RCE bypass CVE-2026-12045 was meant to close, reachable via the same indirect prompt-injection delivery (an attacker plants the payload in any object the AI Assistant may read; the LLM emits it as a tool call).<br /> <br /> An initial candidate fix ran the query with psycopg&amp;#39;s execute(..., prepare=True), intending to force PostgreSQL&amp;#39;s own Parse step (extended query protocol) to reject multi-statement text regardless of sqlparse&amp;#39;s classification. This candidate fix does not work as submitted: psycopg3&amp;#39;s PrepareManager silently ignores the prepare argument whenever the connection&amp;#39;s prepare_threshold is None, which is pgAdmin&amp;#39;s default for every server connection (the per-server "Prepare threshold" field is blank unless an administrator explicitly sets it) -- psycopg3 falls back to the simple query protocol, the same multi-statement-capable path the bypass exploits, so the candidate fix closes nothing on any real-world default configuration.<br /> <br /> The corrected fix sets conn.prepare_threshold = 0 directly on the dedicated, single-use read-only connection the AI Assistant tool opens, structurally forcing the extended query protocol independent of any server-level configuration. Verified against a live PostgreSQL 18 instance: the payload executes successfully under the prepare_threshold=None (default) behavior, and is rejected with "cannot insert multiple commands into a prepared statement" once prepare_threshold=0 is set on that connection.<br /> <br /> This issue affects pgAdmin 4: from 9.13 before 9.17.