CVE-2026-116251 — pgAdmin 4: A user's other sessions survive a change of their password
pgAdmin 4 did not invalidate a user's existing sessions when their password changed, either through the user's own change password dialog or through an administrator resetting it in User Management. A session established before the change, for example on another device or by someone who had obtained the old password or a session cookie, therefore stayed logged in after the change, which is the step a user or administrator takes precisely to cut such access off. It remained usable until it expired. The fix rotates the user's session identifier (fs_uniquifier) whenever the password is changed, so every other session of that user is logged out. The session that made the change is logged in again and keeps its database connections. Saved server passwords, including those for shared servers, are re-encrypted under the new key; any that cannot be decrypted are cleared and the user is told. If re-encryption fails, the sessions are still revoked and the saved passwords are cleared rather than the change failing. This issue affects pgAdmin 4: before 9.19.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Technical severity (medium)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Pgadmin.org pgAdmin 4).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Pgadmin.org | pgAdmin 4 | < 9.19 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 2.3 | CVSS 4.0 | Low | — | — | f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 via NIST National Vulnerability Database |
| 2.3 | CVSS 4.0 | Low | — | — | PostgreSQL via CVE Program (cve.org) e CISA ADP |
| 4.2 | CVSS 3.1 | Medium | 1.6 | 2.5 | f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 via NIST National Vulnerability Database |
| 4.2 | CVSS 3.1 | Medium | — | — | PostgreSQL via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N (score shown at the top: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · pgadmin.org/pgadmin 4
- Record published
- CVSS changed · 4.2
- Source status changed · → Received
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× References added · Oct 30, 2026 – Oct 30, 2026
- 1× Official description updated · Oct 30, 2026 – Oct 30, 2026
References
2 on the record
Elsewhere on this site
Related CVEs (same products)
- Medium CVE-2026-116252 pgAdmin 4: Materialized view refresh redirects its connection through a crafted database name 1d
- Medium CVE-2026-116250 pgAdmin 4: Files opened in a storage directory follow a symbolic link, hard link or FIFO planted after the containment check 1d
- High CVE-2026-116249 pgAdmin 4: Connection file paths and parameter keys escape the user's storage directory 1d
- High CVE-2026-116245 pgAdmin 4: Connection services are not restricted in server mode 1d
- Medium CVE-2026-116248 pgAdmin 4: Non-administrators can share a server with every user 1d
- High CVE-2026-116244 pgAdmin 4: libpq uses the pgAdmin service account's Kerberos credentials 1d
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No FIRST EPSS score.
- No fixed version, patch or mitigation documented.
- No CISA SSVC assessment.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-116251 is "pgAdmin 4: A user's other sessions survive a change of their password", rated Medium. It affects pgAdmin 4 (Pgadmin.org); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 4.2 describes technical severity. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.