Live › vulnerability › CVE-2026-116244
When Kerberos delegation was not intended, pgAdmin dropped KRB5CCNAME, so libpq used the operating-system service account's default Kerberos ticket or keytab. In server mode, any pgAdmin user can then authenticate to a GSSAPI-enabled database server as that service account's principal, regardless of the user name given.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-30 20:25 UTC. All times on this page are UTC.
Teams running pgAdmin 4 in server mode, shared by several users, where connections can use Kerberos or GSSAPI and the pgAdmin service account has a Kerberos ticket or keytab. The sources say gssencmode=disable did not prevent the issue, and the Windows SSPI path behaves the same way. Single-user desktop installs without shared server mode are less exposed, though the sources do not address them directly.
No product ranges from the sources yet.
9.19 are affected.9.19 or later.require_auth setting the fix uses.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
When a pgAdmin 4 connection was not meant to use a Kerberos user's delegated credentials, pgAdmin removed KRB5CCNAME from its environment, so the Kerberos library fell back to the default credential cache, or a client keytab, of the operating-system account running pgAdmin. libpq then answered any server that asked for GSSAPI authentication with that account's ticket, whatever user name the pgAdmin user gave, so in server mode any user could connect as the service account's Kerberos principal; gssencmode=disable did not prevent it. On Windows, SSPI used the service account's logon in the same way. psql was also started with pgAdmin's environment, which could hold another user's credential cache while that user was connecting.
The fix points KRB5CCNAME and KRB5_CLIENT_KTNAME at a file that cannot exist except while a Kerberos-authenticated user connects with Kerberos, and gives every other connection, psql and the utilities require_auth=!gss,!sspi and gssencmode=disable, checked on the final connection string. require_auth needs libpq 16 or later.
This issue affects pgAdmin 4: before 9.19.
This page as .md · .json · in your agent: get_signal("CVE-2026-116244")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.