pgadmin.org pgAdmin up to 9.18 Kerberos Credential default credentials

Summaryinfo

A vulnerability classified as critical has been found in pgadmin.org pgAdmin up to 9.18. Impacted is an unknown function of the component Kerberos Credential Handler. This manipulation causes default credentials. The identification of this vulnerability is CVE-2026-116244. It is possible to initiate the attack remotely. There is no exploit available. It is recommended to upgrade the affected component.

Detailsinfo

A vulnerability was found in pgadmin.org pgAdmin up to 9.18. It has been declared as critical. Affected by this vulnerability is some unknown processing of the component Kerberos Credential Handler. The manipulation with an unknown input leads to a default credentials vulnerability. The CWE definition for the vulnerability is CWE-1392. The product uses default credentials (such as passwords or cryptographic keys) for potentially critical functionality. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:

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.

It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-116244 since 10/25/2026. The exploitation appears to be easy. The attack can be launched remotely. The technical details are unknown and an exploit is not publicly available.

Upgrading to version 9.19 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Vendor

• pgadmin.org

Name

• pgAdmin

Version

• 9.0
• 9.1
• 9.2
• 9.3
• 9.4
• 9.5
• 9.6
• 9.7
• 9.8
• 9.9
• 9.10
• 9.11
• 9.12
• 9.13
• 9.14
• 9.15
• 9.16
• 9.17
• 9.18

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion