Skip to main content
No exploitation reportedFix available

CVE-2026-116246

pgAdmin 4: Server passwords are left in pgAdmin's process environment

No exploitation reported by the sources we read.

  • Published2026-10-30
  • Fixed in9.19
  • WeaknessCWE-214 · CWE-526

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

To pass a server's password to psql and to the utilities pgAdmin 4 runs as background processes, the server manager wrote it into pgAdmin's own process environment: as PGPASSWORD for the PSQL tool, and under a per-process variable for a utility. Nothing removed it afterwards. pgAdmin's environment is shared by every user's requests and copied into every process it starts, so in server mode another user's later PSQL session or utility inherited the password, and libpq used PGPASSWORD for any connection made without a password of its own, letting one user connect with another user's saved password. The fix puts the password only into the environment built for the process that needs it and starts psql with a copy of pgAdmin's environment instead of the environment itself. This issue affects pgAdmin 4: before 9.19.

Timeline

dates in UTC
  1. 2026-10-3020:17CVE publishedNVD

Versions per branch

NVD
Pgadmin pgadmin 4
BranchAffectedFixed in
9.19< 9.199.19

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Fix

  1. Update Pgadmin pgadmin 4 to 9.19

Advisories and patches

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Metasploit modules
none listed
Metasploit Framework

Sources

  • CNACVSS 4.07read 2026-11-04
  • CNACVSS 3.16.5read 2026-11-04
  • NVDCVSS 3.17.6read 2026-11-04
  • CNAweakness (CWE)CWE-214, CWE-526read 2026-11-04
  • FIRST EPSSEPSS score0.2 %2026-11-04
  • GitHub Advisoriesadvisory—

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N
CVSS 4.0 vector
CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:P/VC:H/VI:N/VA:N/SC:H/SI:L/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Published
2026-10-30
Last Modified
2026-11-04
NVD status
Analyzed
GitHub Advisory
GHSA-835v-3mj2-2w29

Frequently asked questions

What is CVE-2026-116246?

To pass a server's password to psql and to the utilities pgAdmin 4 runs as background processes, the server manager wrote it into pgAdmin's own process environment: as PGPASSWORD for the PSQL tool, and under a per-process variable for a utility. Nothing removed it afterwards. pgAdmin's environment is shared by every user's requests and copied into every process it starts, so in server mode another user's later PSQL session or utility inherited the password, and libpq used PGPASSWORD for any connection made without a password of its own, letting one user connect with another user's saved password. The fix puts the password only into the environment built for the process that needs it and starts psql with a copy of pgAdmin's environment instead of the environment itself. This issue affects pgAdmin 4: before 9.19.

Is CVE-2026-116246 actively exploited?

Active exploitation of CVE-2026-116246 has not been confirmed. Its EPSS score was 0.2% on 2026-11-04, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2026-116246?

CVE-2026-116246 has a CVSS v3 base score of 7.6 (HIGH severity), with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, November 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record