Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

Skip to content
cve.new Create a CVE report
Check your stack
CVE-2026-116246high7.0

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

Impact

pgAdmin 4, before version 9.19, stores server passwords in its process environment, allowing other users to access them. This weakness affects server mode, where another user's session can inherit the password. The issue is due to the storage of sensitive information in environment variables.

Summarized by @cf/meta/llama-3.3-70b-instruct-fp8-fast. Verify details against the original sources.

Affected packages

This source has no supported package-version data for matching. You can read the advisory here, but this record alone cannot power a dependency check.

Affected products

Vendor version evidence. Product records are separate from automatic dependency matching.

pgadmin.org · PostgreSQL

pgAdmin 4

1 range
PostgreSQL version evidence

Compare with this publisher’s ranges. This does not inspect your installation.

affected

0 → before 9.19

custom versions

unaffected

unknown

Other versions: unaffected

Original source 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.

Inside the record

Evidence available

Package identity · not supplied
Version evidence
Remediation guidance · not supplied
Weakness classification
Additional publishers · not supplied

Describes the evidence in this view, not whether the product is safe.

Original records

CVE-2026-116246

View the latest unmodified CVE JSON from the official source. It may be newer than this imported page.

cve.new JSON →

Underlying weaknesses

The source’s classification of what caused the vulnerability.

CWE-214 ↗

CWE-214 Invocation of Process Using Visible Sensitive Information

PostgreSQL

Related →
CWE-526 ↗

CWE-526 Cleartext Storage of Sensitive Information in an Environment Variable

PostgreSQL

Related →
Contributing organizations · 1
PostgreSQL

Assigning organization

2026-10-30

What changed

Follow changes
No substantive changes have been recorded here yet. History starts when cve.new observes a change after tracking is enabled; earlier edits are not reconstructed.

Large field values are marked as truncated previews. Original source snapshots remain retained.

References

2 sources
github.com/pgadmin-org/pgadmin4/commit/0eefa38f774dce07c1f939d87f2993b36e2313b9
patchPostgreSQL
github.com/pgadmin-org/pgadmin4/issues/10653
issue-trackingPostgreSQL