CVE-2026-14681

PostgreSQL improper enforcement of GSSAPI encryption when coupled with SSL

Assigner: PostgreSQL
Reserved: 03.07.2026 Published: 13.08.2026 Updated: 13.08.2026

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.5 and 17.11 are affected. Versions before PostgreSQL 17 are unaffected.

Metrics

CVSS Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
CVSS Score: 4.2

Attack Vector	Network	Scope	Unchanged
Attack Complexity	High	Confidentiality Impact	Low
Privileges Required	Low	Integrity Impact	Low
User Interaction	None	Availability Impact	None

CVSS 3.1

Product Status

Vendor	n/a
Product	PostgreSQL
Versions	Default: unaffected affected from 18 to 18.5 (excl.) affected from 17 to 17.11 (excl.)

Vendor

n/a

Product

PostgreSQL

Versions

Default: unaffected

affected from 18 to 18.5 (excl.)
affected from 17 to 17.11 (excl.)

Affected Configurations

pg_hba.conf entries would otherwise require GSSAPI

Credits

The PostgreSQL project thanks p4p3r for reporting this problem.

References

Problem Types

Improper Enforcement of Message Integrity During Transmission in a Communication Channel CWE