---
id: CVE-2026-116247
title: >-
  pgAdmin 4: libpq uses the pgAdmin service account's own password file and
  client certificate
summary: >-
  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…
severity: high
cvss: 8.2
cvssVector: 'CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:N'
cvssSource: cna
cwe:
  - CWE-522
  - CWE-1188
vendor: pgadmin.org
product: pgAdmin 4
affected:
  - pgadmin_4 < 9.19
published: '2026-10-30'
updated: '2026-10-30'
sourceUpdated: '2026-10-30T19:55:16.935Z'
source: CVEORG
sourceUrl: 'https://www.cve.org/CVERecord?id=CVE-2026-116247'
references:
  - url: 'https://github.com/pgadmin-org/pgadmin4/issues/10652'
  - url: >-
      https://github.com/pgadmin-org/pgadmin4/commit/32db693198f28b78fe2af12a726b80a68eb78cb2
tags:
  - cve.org
epss: 0.00127
epssPercentile: 0.02393
ingestedAt: '2026-11-05T16:24:31.429Z'
---

## Overview

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.

## Affected

- `pgadmin_4 < 9.19`

## Remediation

Refer to the linked advisories for vendor-supplied fixes and affected version ranges.