Description
Improper enforcement of message integrity in PostgreSQL GSSAPI support allows a user to negotiate GSSAPI contrary to pg_hba.conf rules, via initial direct TLS connection. Despite a pg_hba.conf that appears to require GSSAPI, the connection may exchange data over TLS encryption alone. If the TLS settings are more permissive than the GSS settings, the connection may continue with lesser protection. Within major versions 17-18, minor versions before PostgreSQL 18.6 and 17.11 are affected. Versions before PostgreSQL 17 are unaffected.
Affected products
postgresql: postgresql
References1
- www.postgresql.org/support/security/CVE-2026-14681/ Vendor Advisory
Metrics
- CVSS 3.1
-
4.2
MEDIUM
Score source: CNA
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N - EPSS — exploit probability
- 0% percentile: 0 · as of 12 November 2026
- CWE
- CWE-924
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.