CVE-2026-116244
Last modified
CVE-2026-116244 is a high-severity vulnerability rated 8.2/10 on the CVSS scale. 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.
Description
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.
Metrics
Weakness Enumeration
Affected Software
Source: CNA advisory (CVE.org). NVD analysis pending.
| Vendor | Product | Versions |
|---|---|---|
| pgadmin.org | pgAdmin 4 | < 9.19 |
References
Timeline
- Published
- Last Modified
- Status
- Received
Frequently Asked Questions
What is CVE-2026-116244?
How severe is CVE-2026-116244?
How do I fix CVE-2026-116244?
How Strix Helps
- How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
- Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
- PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
- AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.
Related CVEs from 2026
- CVE-2026-116239In server mode pgAdmin 4 keeps an account per authentication…8.5
- CVE-2026-11624The Model Context Protocol has a security warning advising s…9.4
- CVE-2026-116240In server mode pgAdmin 4 validates a path into the user's st…6.5
- CVE-2026-116241pgAdmin 4's Import/Export Data tool wraps a user's query exp…9.9
- CVE-2026-116242pgAdmin 4 opens SSH tunnels with the sshtunnel library but g…8.2
- CVE-2026-116243pgAdmin 4 runs pg_dump, pg_restore, pg_dumpall and psql from…7.5
- CVE-2026-116245libpq looks a connection service up in the service file of t…8.2
- CVE-2026-116246To pass a server's password to psql and to the utilities pgA…6.5
- CVE-2026-116247When a server in pgAdmin 4 had no password file, client cert…8.2
- CVE-2026-116248In pgAdmin 4 server mode only administrators are meant to sh…6.8
- CVE-2026-116249In server mode pgAdmin 4 resolves a server's password file, …8.4
- CVE-2026-11625Bytes::Random::Secure versions through 0.29 for Perl share i…7.5
Are you affected by CVE-2026-116244?
Run a free Strix scan to check your systems for this vulnerability.
Scan your code nowSource: NVD / NIST
