CVE-2026-17566 Details
Description
pgAdmin 4's Import/Export Data tool builds a psql \copy (...) command line by interpolating a user-supplied SQL query into a Jinja template and passing the rendered line to psql via --command. To stop an attacker from breaking out of the (...) wrapper, create_import_export_job() (route POST /import_export/job/<sid>, gated only by the ordinary, commonly-granted tools_import_export_data permission) validated the query with a hand-written parenthesis-balance checker, _is_query_parens_balanced(). That checker always treated a backslash before a single quote (\') as escaping the quote, i.e. as if standard_conforming_strings were off. PostgreSQL has defaulted standard_conforming_strings to on since 9.1 (2010), the default on every PostgreSQL version pgAdmin 4 currently supports (13-18); under that default psql's own \copy tokenizer treats \ as an ordinary character, so a single quote immediately after it closes the string literal. A query such as SELECT 'a\') TO PROGRAM 'echo pwned' x' was therefore accepted as "balanced" by pgAdmin's checker (which believed the ) was still inside the string), while psql, run through the actual rendered command line, closes the string at that point and treats the following ) as the end of the wrapping \copy (...) subquery, exposing an attacker-chosen TO PROGRAM '<command>' clause that psql executes via popen() -- independent of a subsequent syntax error later on the same line. This is the same class of bug as CVE-2025-12762/CVE-2025-13780 (RCE via psql meta-command/COPY injection during PLAIN-format dump restore), reached through an independently written defense in a different module (Import/Export Data rather than Restore) that had its own, different logic bug (inverted backslash-escape semantics rather than a BOM-defeated regex anchor). The fix rejects any backslash inside a single-quoted string in the query outright, rather than picking one of the two possible psql interpretations. This is intentionally conservative: because the correct interpretation of \ depends on the target server's standard_conforming_strings setting, which the checker cannot reliably know at validation time, refusing the query is safer than guessing. This issue affects pgAdmin 4: from the introduction of _is_query_parens_balanced() before 9.18.
A command injection vulnerability has been identified in pgAdmin 4 versions prior to 9.17, within the Import/Export Data tool. The issue arises from a backslash-escape mismatch in the query validation process. The tool constructs a psql \\copy command by interpolating user-supplied SQL queries into a Jinja template, which is then executed via the --command option. To prevent users from breaking out of the \\copy command's parentheses, pgAdmin 4 implemented a parenthesis-balance checker. However, this checker incorrectly handled backslashes before single quotes as escape characters, which is only valid when standard_conforming_strings is turned off. Since PostgreSQL has had standard_conforming_strings enabled by default since version 9.1, and all supported pgAdmin 4 versions have this default, the psql tokenizer treats backslashes as regular characters under this setting. This allows an attacker to craft a query that escapes the string literal and injects commands through a TO PROGRAM clause, achieving remote code execution.
Users can upgrade to pgAdmin 4 version 9.17 or later, where this vulnerability has been fixed.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
CISA-ADP
Assessed Jul 31, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
| URL | Source(s) | Tag(s) |
|---|---|---|
| https://github.com/pgadmin-org/pgadmin4/commit/1496fabe28c9f825f6bac0f0d000d9d3276322c3 | PostgreSQL | Patch |
| https://github.com/pgadmin-org/pgadmin4/issues/10213 | PostgreSQL | Issue TrackingPatch |
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-115 | Misinterpretation of Input | PostgreSQL |
| CWE-78 | Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') | PostgreSQL |
Affected Products
| Product | Versions |
|---|---|
| pgadmin pgadmin 4 | < 9.18 |
CPE
Remediation
| |
Change History
5 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Oct 23, 2026 | CVE Translated | [email protected] |
| Aug 5, 2026 | Initial Analysis | [email protected] |
| Aug 1, 2026 | CVE Modified | CISA-ADP |
| Jul 31, 2026 | CVE Modified | CISA-ADP |
| Jul 31, 2026 | New CVE Received | PostgreSQL |