Libpq Looks a Connection Service Up
Source GCVE Database
Not known to be exploited · CVSS 8.2 High : upgrade to 9.19 soon.
Data as of 30 Oct 2026, 23:26 UTC
Thin evidence
One scorer or none| CNA (PostgreSQL) | CVSS 3.1 | 8.2 |
|---|---|---|
| CNA (PostgreSQL) | CVSS 4.0 | 7.1 |
- Patch
- Available – fixed in 9.19
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:NExploitation 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.
What to do
Upgrade pgAdmin 4 to 9.19.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| pgadmin.orgpgAdmin 4 | Affected
| Fixed in
|
GitHubpgAdmin 4pkg:github/pgAdmin 4Other threats | Affected
| Fixed in
|
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, which includes the SERVER_MODE_ALLOWED_SERVICES setting to restrict allowed connection services and removes sensitive environment variables at startup. Until upgraded, restrict access to the operating system account's service file and environment variables to trusted users only.
Description
A vulnerability in pgAdmin 4 before version 9.19 allows any user in server mode to specify a connection service from the operating system account's service file, potentially using stored credentials such as passwords or client certificates. This occurs because libpq looks up connection services in the service file of the OS account running pgAdmin 4 and uses environment variables like PGPASSWORD or PGSERVICE without restriction. The issue is addressed by introducing the SERVER_MODE_ALLOWED_SERVICES setting, which restricts allowed services and removes sensitive environment variables at startup.