Skip to main content
VulnerabilityPublished

CVE-2026-116246: pgAdmin 4 · Invocation of Process Using Visible Sensitive Information

Affects pgAdmin 4Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 9.19 when convenient.

Data as of 30 Oct 2026, 20:38 UTC

CVSS 3.1 base score
6.5Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (PostgreSQL)CVSS 3.16.5
CNA (PostgreSQL)CVSS 4.07.0
Patch
Available – fixed in 9.19
CVSS:3.1/AV:N/AC:H/PR:L/UI:R/S:C/C:H/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 30 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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

ProductAffectedFixed in
pgadmin.orgpgAdmin 4Affected
  • <9.19
Fixed in
  • 9.19
GitHubpgAdmin 4pkg:github/pgAdmin 4Other threatsAffected
  • <9.19
Fixed in
  • 9.19

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, where the vulnerability is fixed by isolating password environment variables to individual processes. No other mitigation is required as the fix addresses the root cause.

Description

CVE-2026-116246 is a vulnerability in pgAdmin 4 before version 9.19 where server passwords were exposed in the process environment. Passwords were stored in environment variables shared across user requests and inherited by background processes, allowing one user to access another user's saved password. This issue was fixed in version 9.19 by isolating the password environment to only the specific process that requires it.

References

Community reviews

Loading reviews…