CVE.org (no NVD analysis yet)· CNA PostgreSQL

CVE-2026-116241: pgAdmin 4: Import/Export Data query export runs a command through a backslash in a double-quoted identifier

CriticalCVSS 9.4 · v4.0—No exploit No fix recorded

Noroxi assessment

Priority: Monitor (action score 37/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.31% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
No fixed version is recorded, but the references include a patch (commit or PR) link.

Low priority for now. See the fix and affected versions sections below.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

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.

EUVD-2026-114382

Published: Oct 30, 2026
Updated: Nov 6, 2026
EPSS: 0.3% · 24th percentile
CWE: CWE-78

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 37 / 40 · 9.4 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: total

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: —
CNA · PostgreSQL: 9.9; NVD has not scored this yet; the score shown is the CNA’s.

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
No fixed version yet

If any of these changes, we'll tell you in the daily email digest.

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
pgadmin	pgadmin 4	cpe:2.3:a:pgadmin:pgadmin_4

Versions reported by the vendor

Affected version ranges reported by the assigning authority (PostgreSQL). Independent of NVD's CPE analysis and usually ahead of it.

pgadmin.org pgAdmin 4
- before 9.19affected

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

pgadmin pgadmin 4before 9.19

Same product

pgadmin: all records

Other highest-scoring records for the same primary product.

CVE-2024-2044Unsafe Deserialisation and Remote Code Execution by an Authenticated user in pgAdmin 4
63This week
CVE-2024-3116Remote Code Execution Vulnerability through the validate binary path API in pgAdmin 4
60This week
CVE-2022-4223The pgAdmin server includes an HTTP API that is intended to be used to validate the path a user selects to external PostgreSQL utilities…
59Plan

Published before and after this one in the same product

← EarlierCVE-2026-116239Oct 30, 2026 · pgAdmin 4: An LDAP or Kerberos login is logged in to another account with the same username
35Monitor
← EarlierCVE-2026-116240Oct 30, 2026 · pgAdmin 4: File Manager and storage-path tools act on a different path from the one checked
28Monitor
Later →CVE-2026-116242Oct 30, 2026 · pgAdmin 4: SSH tunnels use the pgAdmin service account's own SSH identity
28Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

No fix version is recorded for this entry. Check the references for vendor advisories.

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

EPSS, last 120 days

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

pgadmin-org/pgadmin4commit 9be31a0

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

Yonghwa Lee (Xint by Theori) <underdog@theori.io>finder
Dave Page <dpage@pgadmin.org>remediation developer
Hitesh Jambhale <hitesh.jambhale@enterprisedb.com>remediation reviewer
Ashesh Vashi <ashesh.vashi@enterprisedb.com>remediation reviewer

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2026-1756691 days apartpgAdmin 4: RCE via backslash-escape mismatch in Import/Export Data query guard (incomplete defense, sibling gap to CVE-2025-13780)
37Monitor
CVE-2025-12763351 days apartCommand injection vulnerability allowing arbitrary command execution on Windows
35Monitor
CVE-2026-7816172 days apartpgAdmin 4: OS command injection in Import/Export query export via psql metacommand breakout
34Monitor
CVE-2026-1734791 days apartpgAdmin 4: OS command injection in MASTER_PASSWORD_HOOK via untrusted username substitution
30Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

CVE-2026-8686343 days apartpgAdmin 4: Authentication bypass via a client-controlled identity header in Webserver authentication mode
37Monitor
CVE-2026-1162390 days apartpgAdmin 4: An LDAP or Kerberos login is logged in to another account with the same username
35Monitor

Not on record for this CVE: public bounty program.

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality
Integrity
Availability

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: X

Weakness class (CWE)

CWE-78 · Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

CVSS vector

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

nvd-secondary

Root cause

User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.

The bug in code

The whole CWE-78 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const host = req.body.host;
2exec("ping -c 1 " + host, onResult);

Fixed

1const host = req.body.host;
2if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);
3execFile("ping", ["-c", "1", host], onResult);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

SSVC exploitation— → noneNov 6, 2026, 6:07 PM UTC
CVSS9.9 → 9.4Nov 2, 2026, 2:07 PM UTC
Exploit maturity— → noneOct 30, 2026, 11:07 PM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/pgadmin-org/pgadmin4/commit/9be31a019f780647fb689c458408c8803263c812

Show all references (1 more)

github.com/pgadmin-org/pgadmin4/issues/10663

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records