CVE-2026-86862Network attack vectorHinoki check available

Credential disclosure via database connection-string injection

Published Sep 17, 2026 · Updated Sep 17, 2026

Connection-string injection in pgAdmin 4 before 9.18 allows remote authenticated users to expose database passwords via Restore or Maintenance. These tools pass the client-supplied database field as --dbname to pg_restore or psql; libpq interprets values containing an equals sign as connection parameters, overriding the intended endpoint and sending the decrypted PGPASSWORD credential to an attacker-selected server. Exploitation requires a connected server and tools_restore or tools_maintenance permission, granted by the default User role; it also enables outbound connections to internal addresses but does not itself alter data or interrupt pgAdmin.

CVSS severity7.1
High
EPSS probability0.35%
Next 30 days · Oct 19, 2026
Known exploitationUnconfirmed
Based on sourced intelligence
Hinoki checkAvailable
Coverage for this vulnerability

See if you're affected

Explore vulnerability checks for your environment with Hinoki.

Get started

Summary

What happened

Connection-string injection in pgAdmin 4 before 9.18 allows remote authenticated users to expose database passwords via Restore or Maintenance. These tools pass the client-supplied database field as --dbname to pg_restore or psql; libpq interprets values containing an equals sign as connection parameters, overriding the intended endpoint and sending the decrypted PGPASSWORD credential to an attacker-selected server. Exploitation requires a connected server and tools_restore or tools_maintenance permission, granted by the default User role; it also enables outbound connections to internal addresses but does not itself alter data or interrupt pgAdmin.

The record

CVE
CVE-2026-86862
Published
Sep 17, 2026
Updated
Sep 17, 2026
Vendor
pgAdmin Development Team
Product
pgAdmin 4
Classifications
CWE-522, CWE-918, CWE-88, T1187
Attack vector
network
Privileges
authenticated

Timeline

How it unfolded

  1. Sep 17, 2026CVE publishedPublication date reported by the CVE source.
  2. Sep 17, 2026Record updatedLatest update available in the CVE record.

Exploitability

Present is not the same as exploitable

Compare your product and version with the public record. A matching version still requires validation against your environment.

Is a vulnerable build present?

Compare these published version ranges with your installed build and any vendor patches.

  1. Affected versionversion=0 <9.18

What conditions does exploitation require?

Attack vectornetwork
Required privilegesauthenticated

What is affected?

pgAdmin Development Team · pgAdmin 4version=0 <9.18

Published CVSS scores

7.1PostgreSQL CNACVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N
6.5PostgreSQL CNACVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CVSS describes severity. EPSS estimates exploitation probability.

Attacks

What attackers are doing with it

Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.

Activity data is delayed. The latest report is Sep 28, 2026.

Daily unique IPsNo honeypot observations are available for this CVE in the selected window.

No observations available

Sep 22, 2026Sep 28, 2026
Latest reporting daySep 28, 2026
Latest daily unique IPsUnavailable
Prior 30-day averageUnavailable
SourceShadowserver honeypots (KEV)
Vectornetwork
Privilegesauthenticated
Known exploitationUnconfirmed
Public exploitUnconfirmed

Weakness, pattern, technique

CWE-522Insufficiently Protected Credentials
CWE-918Server-Side Request Forgery (SSRF)
CWE-88Improper Neutralization of Argument Delimiters in a Command ('Argument Injection')
T1187Forced Authentication

Public exploit references

No public exploit references are available in this record.

Labels summarize the accepted research assessment. They do not indicate a test against your environment.

Technologies

Your stack

See the directory against your own environment.

Your stack

Check the software in your environment

Get started to see how Hinoki identifies affected software and validates exploitability in your environment.

Get started