GSSAPI policy bypass via post-TLS encryption request
Published Aug 13, 2026 · Updated Aug 13, 2026
Message-integrity failure in PostgreSQL 17 before 17.11 and 18 before 18.5 allows remote authenticated users to bypass GSSAPI policy. The core server accepts a GSS encryption request after direct TLS is established, then treats the TLS-only channel as GSS-encrypted for pg_hba.conf matching. Exploitation requires GSSAPI negotiation and a pg_hba.conf policy that requires GSSAPI while allowing less-protective TLS settings.
Summary
What happened
Message-integrity failure in PostgreSQL 17 before 17.11 and 18 before 18.5 allows remote authenticated users to bypass GSSAPI policy. The core server accepts a GSS encryption request after direct TLS is established, then treats the TLS-only channel as GSS-encrypted for pg_hba.conf matching. Exploitation requires GSSAPI negotiation and a pg_hba.conf policy that requires GSSAPI while allowing less-protective TLS settings.
The record
- CVE
- CVE-2026-14681
- Published
- Aug 13, 2026
- Updated
- Aug 13, 2026
- Vendor
- PostgreSQL Global Development Group
- Product
- PostgreSQL
- Classifications
- CWE-924, T1210
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 13, 2026CVE publishedPublication date reported by the CVE source.
- Aug 13, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=17 <17.11
- Affected versionversion=18 <18.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo