CVE-2026-14681
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.
Does this matter?
Lower severity and a low EPSS score (0.07%). Track it; it rarely justifies an emergency change on its own.
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.
- CVSS 3.1
- 4.2 MEDIUMCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
- EPSS
- 0.07% probability · 0th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-924
- Affected
- postgresql/postgresql
- Source
- f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
References
- https://www.postgresql.org/support/security/CVE-2026-14681/Vendor Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.