CVE-2026-116241
9.9 CRITICALpublic exploit availablePublished 2026-10-30 · Updated 2026-10-30
AI risk analysis
- Summary
- pgAdmin 4's Import/Export Data tool incorrectly validated SQL queries by rejecting backslashes in single-quoted strings but not in double-quoted identifiers, allowing an attacker to bypass the wrapper and inject a psql TO PROGRAM clause that executes arbitrary commands on the host as the pgAdmin service account.
- Exploitability
- Exploitation requires valid database credentials (low-privilege roles suffice) and the ability to craft a malicious query with a backslash-escaped double quote inside a double-quoted identifier, which is feasible due to inconsistent quoting handling between pgAdmin's validation and psql's parser when standard_conforming_strings is disabled.
- Blast radius
- Successful exploitation grants remote code execution on the pgAdmin host as the service account, potentially compromising the entire system and enabling lateral movement within the database environment.
- Detection
- Monitor for psql command-line invocations containing 'TO PROGRAM' in pgAdmin service logs or process execution logs on the host; also watch for unexpected child processes spawned by the pgAdmin service with non-standard command-line arguments.
- Prioritized remediation
- Upgrade to pgAdmin 4 version 9.19 or later, which patches the validation logic to reject backslashes in double-quoted identifiers.
Analysis generated locally by garnet-coder (no data left the box). AI-assisted — verify against primary sources before acting.
NVD description
pgAdmin 4's Import/Export Data tool wraps a user's query export in a psql \copy (...) TO command and checks that the query's parentheses are balanced so that nothing can escape the wrapper. The check rejected a backslash inside a single-quoted string, but not inside a double-quoted identifier, where it treated the next double quote as closing the identifier. psql's \copy parser applies the connection's escape character to whichever quote opened a token, so with standard_conforming_strings off a backslash-escaped double quote does not close the identifier. pgAdmin's and psql's view of the quoting then diverged, a closing parenthesis hidden from the check ended the \copy (...) wrapper, and a following TO PROGRAM clause was executed by psql on the pgAdmin host, as the operating-system account running pgAdmin, before the server rejected the statement. An ordinary database role can turn standard_conforming_strings off for itself, and the Import/Export Data permission is granted to non-administrators by default. This is a bypass of the fix for CVE-2026-17566. The fix rejects any backslash inside a double-quoted identifier, as was already done for single-quoted strings, since its meaning depends on a server setting that cannot be known reliably when the query is validated. This issue affects pgAdmin 4: before 9.19.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Weaknesses
CWE-78, CWE-115
Public exploit & PoC references
All references
Source data: NVD (nvd.nist.gov), public domain. Exploit-DB.ai adds local AI analysis for defensive use only.
Related CVEs
- CRITICALCVE-2023-54399
- CRITICALCVE-2023-54400PoC
- CRITICALCVE-2025-63564
- HIGHCVE-2026-100683PoC
- CRITICALCVE-2026-103244PoC
- CRITICALCVE-2026-104354
- HIGHCVE-2026-104457PoC
- CRITICALCVE-2026-105489
Related by shared AI tags and CWE weakness class. Browse the full archive.