Vulnerability in PostgreSQL
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. 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.
Published · last modified .
CVSS v3 metric
CVSS v3 base score 4.2 (Medium). Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N.
EPSS exploit prediction
EPSS: 0.001 (0.0th percentile), scored .
Very low probability of exploitation in the next 30 days; routine patching cadence is appropriate. 0th percentile — 0.0% of CVEs in the catalogue have a lower EPSS than this one. How to read EPSS.
EPSS over last 30 days · oldest: 0.001 · newest: 0.001 · change: 0.000
Affected products
- PostgreSQL
- PostgreSQL — versions 18, 17
Weakness classification (CWE)
References
- f86ef6dc-4d3a-42ad-8f28-e6d5547a5007 (Vendor Advisory)
Frequently asked questions
- What is CVE-2026-14681?
- CVE-2026-14681 is a medium-severity vulnerability in PostgreSQL, classified under Improper Enforcement of Message Integrity During Transmission in a Communication Channel. CVSS score: 4.2/10. Published 2026-08-13.
- How severe is CVE-2026-14681?
- Medium severity. CVSS v3 base score is 4.2 out of 10.