pgAdmin 4: Invocation of Process Using Visible Sensitive Information
CVE-2026-116246 is a high-severity invocation of process using visible sensitive information vulnerability in pgAdmin 4 from Pgadmin.org, with a CVSS 3.1 base score of 7.6 out of 10. It can be exploited remotely over the network by an attacker with a low-privileged account, but only if a user takes part, for example by opening a link or file. The record lists version 9.19 as the first without the flaw, so updating pgAdmin 4 to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 0.19% chance of exploitation within 30 days, which is low compared with other CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update pgAdmin 4 to 9.19 or a later version.
- Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Pgadmin.org | pgAdmin 4 | before 9.19 | 9.19 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- LowA basic user account is enough.
- User interaction
- RequiredA user must take an action such as opening a file or link.
- Scope
- ChangedThe attack can reach beyond the vulnerable component into other systems.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:L/A:N. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 4.0 | 7.0 | High | CNA |
| CVSS 3.1 | 6.5 | Medium | CNA |
| CVSS 3.1 | 7.6 | High | NVD |
Official 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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Invocation of Process Using Visible Sensitive Information
A process is invoked with sensitive command-line arguments, environment variables, or other elements that can be seen by other processes on the operating system.
More Invocation of Process Using Visible Sensitive Information vulnerabilities (CWE-214)
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: none, automatable: no, technical impact: partial).
- Record last changed materially (score, affected products, status or references).
References
Patches and release notes
Other references
- github.com/pgadmin-org/pgadmin4/issues/10653Issue Tracking
Other vulnerabilities in pgAdmin 4
- 9.6 Critical severity
- 9.6 Critical severity
- 9.6 Critical severity
- 9.6 Critical severity
- 8.8 High severity
- 9.6 Critical severity
Recent Invocation of Process Using Visible Sensitive Information vulnerabilities
- 7.1 High severity
- 7.9 High severity
- 7.5 High severity
- 7.1 High severity
Spotted an error? Tell us.