{"id":"CVE-2026-116251","aliases":[],"cve":{"records":[{"id":"CVE-2026-116251","source":"PostgreSQL","state":"PUBLISHED","reasons":[],"replacements":[],"disputed":false,"unsupportedWhenAssigned":false,"reserved":"2026-10-25T16:26:16.420Z","published":"2026-10-30T19:55:19.613Z","modified":"2026-10-30T19:55:19.613Z"}],"publishers":[{"name":"PostgreSQL","role":"CNA","organizationId":"f86ef6dc-4d3a-42ad-8f28-e6d5547a5007","modified":"2026-10-30T19:55:19.613Z"}],"references":[{"url":"https://github.com/pgadmin-org/pgadmin4/issues/10646","tags":["issue-tracking"],"source":"PostgreSQL"},{"url":"https://github.com/pgadmin-org/pgadmin4/commit/67eab1ba891d24209eb0d4bac050dcc8068d93b7","tags":["patch"],"source":"PostgreSQL"}],"weaknesses":[{"id":"CWE-613","description":"CWE-613 Insufficient Session Expiration","source":"PostgreSQL"}],"applicability":[],"prioritization":[]},"title":"pgAdmin 4: A user's other sessions survive a change of their password","titleSource":"PostgreSQL","descriptionSource":"PostgreSQL","description":"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.\n\nThe 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.\n\nThis issue affects pgAdmin 4: before 9.19.","score":4.2,"severity":"medium","published":"2026-10-30T19:55:19.613Z","modified":"2026-10-30T19:55:19.613Z","withdrawn":false,"knownExploited":false,"affected":[],"products":[{"vendor":"pgadmin.org","name":"pgAdmin 4","platforms":[],"versions":[{"version":"0","status":"affected","lessThan":"9.19","versionType":"custom"}],"defaultStatus":"unaffected","cpes":[],"source":"PostgreSQL","url":"https://www.cve.org/CVERecord?id=CVE-2026-116251"}],"remediation":[],"references":["https://github.com/pgadmin-org/pgadmin4/issues/10646","https://github.com/pgadmin-org/pgadmin4/commit/67eab1ba891d24209eb0d4bac050dcc8068d93b7"],"sources":[{"name":"CVE","id":"CVE-2026-116251","modified":"2026-10-30T19:55:19.613Z","url":"https://www.cve.org/CVERecord?id=CVE-2026-116251"}],"assessments":[{"source":"PostgreSQL","vector":"CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N","score":4.2},{"source":"PostgreSQL","vector":"CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N","score":2.3}],"sourceAffected":[],"observedAt":"2026-10-30T20:24:50.110Z","kev":{"status":"not-listed","checkedAt":"2026-10-31T14:10:32.801Z"},"coverage":[{"source":"NVD","status":"not-checked"},{"source":"GHSA","status":"not-checked"},{"source":"EUVD","status":"not-checked"},{"source":"EPSS","status":"not-checked"}],"evidence":[],"aiSummary":{"text":"pgAdmin 4 versions before 9.19 are affected by a weakness where a user's existing sessions remain active after a password change. An attacker with access to an existing session, such as through a stolen session cookie, can continue to use the session until it expires. The issue is due to insufficient session expiration.","model":"@cf/meta/llama-3.3-70b-instruct-fp8-fast","generatedAt":"2026-10-31T05:16:08.300Z","sources":[{"name":"CVE","url":"https://www.cve.org/CVERecord?id=CVE-2026-116251"}]}}