Description
When a server in pgAdmin 4 had no password file, client certificate or client key configured, or the configured one could not be found, pgAdmin left the parameter out of the connection and libpq fell back to the defaults of the operating-system account running pgAdmin: ~/.pgpass, ~/.postgresql/postgresql.crt and postgresql.key, or PGPASSFILE, PGSSLCERT and PGSSLKEY. In server mode any user could therefore connect to a server with the service account's saved passwords or client certificate, and supplying only a copy of its public certificate was enough for libpq to pair it with the service account's private key. A pg_service.conf entry, or a maintenance database name read as a connection string by pg_dumpall, could bring the same files back for the utilities.

The fix gives each of these parameters a value in server mode, the user's own file or otherwise a path that can never be opened, in the connection string, in the environment of the utilities and in the --dbname connection string that ranks above a service entry. Desktop mode is unchanged.

This issue affects pgAdmin 4: before 9.19.
Published: 2026-10-30
Score: 7.1 High
EPSS: n/a
KEV: No
Impact: Unauthorized database access
Action: Immediate patch
AI Analysis

Impact

When pgAdmin 4 runs in server mode without explicit passwords or certificates, it falls back to the operating‑system account’s default credential files. This allows any user who can reach the pgAdmin service to authenticate to PostgreSQL servers using the service account’s stored password or simply provide a copy of the service account’s public certificate. The flaw, categorized as CWE‑1188 and CWE‑522, can result in confidentiality and integrity compromise of database contents by enabling privileged access without knowledge of the actual credentials.

Affected Systems

The vulnerability is present in pgAdmin 4 from pgAdmin.org. All releases older than 9.19 are affected; newer versions contain the fix. The issue only applies to server mode operation, as the desktop mode is unaffected.

Risk and Exploitability

The CVSS score is 7.1 (High). An attacker would need access to the pgAdmin server, either through network reachability or local compromise, to exploit the flaw. The EPSS score is not available, and the vulnerability has not been listed in the CISA KEV catalog. Because libpq silently uses the service account’s credentials, the exploitation path is pragmatic: an attacker can gain database access merely by connecting to the pgAdmin service and presenting the service account’s public key or by providing no credentials at all when none are configured.

Generated by OpenCVE AI on October 30, 2026 at 21:46 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade pgAdmin 4 to version 9.19 or later, which sets a non‑accessible default path for credential parameters in server mode.
  • If an upgrade cannot be performed immediately, explicitly configure PGPASSFILE, PGSSLCERT and PGSSLKEY to point to files that cannot be read by other users, or provide an empty file that the service account cannot access.
  • Ensure that pg_service.conf entries and any pg_dumpall connection strings reference secure credential files and that the pgAdmin service runs under a restricted account with minimal permissions.

Generated by OpenCVE AI on October 30, 2026 at 21:46 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 30 Oct 2026 22:00:00 +0000

Type Values Removed Values Added
First Time appeared Pgadmin
Pgadmin pgadmin 4
Vendors & Products Pgadmin
Pgadmin pgadmin 4

Fri, 30 Oct 2026 20:15:00 +0000

Type Values Removed Values Added
Description When a server in pgAdmin 4 had no password file, client certificate or client key configured, or the configured one could not be found, pgAdmin left the parameter out of the connection and libpq fell back to the defaults of the operating-system account running pgAdmin: ~/.pgpass, ~/.postgresql/postgresql.crt and postgresql.key, or PGPASSFILE, PGSSLCERT and PGSSLKEY. In server mode any user could therefore connect to a server with the service account's saved passwords or client certificate, and supplying only a copy of its public certificate was enough for libpq to pair it with the service account's private key. A pg_service.conf entry, or a maintenance database name read as a connection string by pg_dumpall, could bring the same files back for the utilities. The fix gives each of these parameters a value in server mode, the user's own file or otherwise a path that can never be opened, in the connection string, in the environment of the utilities and in the --dbname connection string that ranks above a service entry. Desktop mode is unchanged. This issue affects pgAdmin 4: before 9.19.
Title pgAdmin 4: libpq uses the pgAdmin service account's own password file and client certificate
Weaknesses CWE-1188
CWE-522
References
Metrics cvssV3_1

{'score': 8.2, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N'}

cvssV4_0

{'score': 7.1, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:N/SC:H/SI:H/SA:N'}


Subscriptions

Pgadmin Pgadmin 4
cve-icon MITRE

Status: PUBLISHED

Assigner: PostgreSQL

Published:

Updated: 2026-10-30T19:55:16.935Z

Reserved: 2026-10-25T16:26:16.419Z

Link: CVE-2026-116247

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Received

Published: 2026-10-30T20:17:04.750

Modified: 2026-10-30T20:17:04.750

Link: CVE-2026-116247

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-30T22:00:15Z

Weaknesses
  • CWE-1188

    Initialization of a Resource with an Insecure Default

  • CWE-522

    Insufficiently Protected Credentials