Is CVE-2026-116251 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-116251 being exploited in the wild.

How severe is CVE-2026-116251?

Medium severity, with a CVSS score of 4.2, published 30 October 2026.

Is there a fix for CVE-2026-116251?

Yes: fixed in pgAdmin 4 9.19. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-116251 attacked?

It is attacked over the network.

Am I affected by CVE-2026-116251?

Check whether you run Pgadmin 4 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-116251: pgAdmin 4 session invalidation failure after password change

CVE-2026-116251 · Severity: medium · CVSS 4.2 · Published 2026-10-30

pgAdmin 4 is a web-based management tool for PostgreSQL databases. When a user changes their password through the settings dialog or an administrator resets it, the application failed to log out the user's other active sessions. This means someone with an old password or a stolen session cookie could continue accessing the application and databases even after the password was changed, defeating the security action intended to revoke unauthorized access.

Technologies: Pgadmin 4. Vendors: pgAdmin.

Quick answers

Is CVE-2026-116251 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-116251 being exploited in the wild.
How severe is CVE-2026-116251?: Medium severity, with a CVSS score of 4.2, published 30 October 2026.
Which products and versions are affected?: Pgadmin 4 before 9.19.
Is there a fix for CVE-2026-116251?: Yes: fixed in pgAdmin 4 9.19. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-116251 attacked?: It is attacked over the network.
Am I affected by CVE-2026-116251?: Check whether you run Pgadmin 4 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: pgAdmin 4 9.19

Technical details

The vulnerability is a session persistence flaw in the authentication mechanism: pgAdmin 4 did not invalidate existing session identifiers (fs_uniquifier) when a password was changed. An attacker with a valid session cookie or knowledge of the old password could maintain access across multiple devices or sessions. The fix rotates the session identifier on password change, forcing re-authentication for all other sessions while preserving database connections for the session performing the change.

Affected products

pgAdmin pgAdmin 4 before 9.19

Timeline

2026-10-30: disclosed

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.