CVE-2026-116241
CRITICALDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Exploit Intelligence
Low risk: more likely to be exploited than 24% of all known CVEs.
References
Related Vulnerabilities
Other CWE-78 (OS Command Injection) vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2021-1498 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2014-6271 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2019-16920 | Critical | 9.8 | 100% | KEV | - |
| CVE-2022-44877 | Critical | 9.8 | 100% | KEV | Fix |
| CVE-2020-8515 | Critical | 9.8 | 100% | KEV | - |
| CVE-2020-9054 | Critical | 9.8 | 100% | KEV | Fix |
Common questions
How do I fix CVE-2026-116241?
Upgrade pgadmin 4 to 9.19 or later.
Is CVE-2026-116241 being actively exploited?
Not that we know of. CVE-2026-116241 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.31% is the estimated probability that it will be exploited in the next 30 days. That is higher than 24% of all scored CVEs.
How severe is CVE-2026-116241?
CVE-2026-116241 has a CVSS v3 base score of 9.9, rated critical. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-116241 affect?
Published advisories record a fix for pgadmin 4 (NVD). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-116241
Markdown
[](https://tridentstack.com/cve/CVE-2026-116241)HTML
<a href="https://tridentstack.com/cve/CVE-2026-116241"><img src="https://tridentstack.com/cve/badge/CVE-2026-116241.svg" alt="CVE-2026-116241"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-11-06.