VulnerabilityPublished 30 Oct 2026

CVE-2026-116252: pgAdmin 4's materialized view refresh passed the target database's name to psql's --dbname argument

Source GCVE Database

Compare

Mentioned vulnerabilities

CVE-2026-86862

Authoritative record:CVE-2026-116252· Medium 6.5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 9.19 when convenient.

Data as of 30 Oct 2026, 23:27 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none

CVSS scores by source
CNA (PostgreSQL)	CVSS 3.1	6.5
CNA (PostgreSQL)	CVSS 4.0	7.1

Patch: Available – fixed in 9.19

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 30 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

ghsa-c8mg-g5cp-g9w7

What to do

Upgrade pgAdmin 4 to 9.19.

Affected software

Product	Affected	Fixed in
pgadmin.orgpgAdmin 4	Affected <9.19	Fixed in 9.19
GitHubpgAdmin 4`pkg:github/pgAdmin 4`Other threats	Affected <9.19	Fixed in 9.19

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade pgAdmin 4 to version 9.19 or later, where the vulnerability is fixed by properly handling the database name through the database_conninfo() helper function. No other mitigation is required as the issue is resolved in this official fix.

Description

pgAdmin 4 versions before 9.19 have a vulnerability in the materialized view refresh feature where the target database name is passed unchanged to psql's --dbname argument. This allows a specially crafted database name containing connection string keywords to override connection parameters, potentially redirecting connections to arbitrary hosts and exposing saved server passwords. The issue was fixed by routing the database name through a helper function to ensure it is treated strictly as a database name.

Impact

An attacker with CREATEDB privileges can create a database with a specially crafted name that causes pgAdmin 4 to redirect psql connections to arbitrary hosts and ports. This leads to exposure of the connecting user's saved server password to the attacker-controlled endpoint. The vulnerability impacts confidentiality but does not affect integrity or availability directly.

Summary

The vulnerability in pgAdmin 4 prior to version 9.19 involves the materialized view refresh functionality passing the target database name directly to the psql command's --dbname argument. libpq interprets a --dbname value containing '=' or a postgresql:// URI as a full connection string, overriding host, port, and other connection settings. Since any role with CREATEDB privileges can create a database with such a crafted name, this flaw enables redirection of the psql process to arbitrary hosts and ports controlled by the attacker. Consequently, the connecting user's saved server password is sent to the attacker-controlled endpoint. This issue was previously addressed for other pgAdmin features (Backup, Restore, Maintenance, Import/Export Data) under CVE-2026-86862, and the fix for materialized view refresh involves using the database_conninfo() helper to enforce strict database name handling.

CWE-88Improper Neutralization of Argument Delimiters in a Command (Argument Injection) (opens in a new tab)
Base weaknessOWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs a string for a command to be executed by a separate component in another control sphere, but it does not properly delimit the intended arguments, options, or switches within that command string.
Implementation · Parameterization
Where possible, avoid building a single string that contains the command and its arguments. Some languages or frameworks have functions that support specifying independent arguments, e.g. as an array, which is used to automatically perform the appropriate quoting or escaping while building the command.
Architecture and Design · Input Validation
Understand all the potential areas where untrusted inputs can enter your product: parameters or arguments, cookies, anything read from the network, environment variables, request headers as well as content, URL components, e-mail, files, databases, and any external systems that provide data to the application.
Implementation · Input Validation
Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a list of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does.
OWASP Cheat Sheets
Abuse Case (opens in a new tab)
Deserialization (opens in a new tab)
Injection Prevention (opens in a new tab)
SQL Injection Prevention (opens in a new tab)
Injection Prevention in Java (opens in a new tab)
OWASP ASVS 4.0.3
V1.5.1 (opens in a new tab)
Attack patterns
Flash Parameter Injection (opens in a new tab)
Using Meta-characters in E-mail Headers to Inject Malicious Payloads (opens in a new tab)
HTTP Parameter Pollution (HPP) (opens in a new tab)
OS Command Injection (opens in a new tab)
Parameter Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 30 Oct 2026, 23:27 UTC

WeaknessesCWE-88

Technical details

References

Community reviews

Related threats