CVE•Published 2026-08-13•Modified 2026-08-29•0 articles on news•5 live references•NVD data

CVE-2026-14681Postgresql · Postgresql

Vulnerability data via NVD (ingested)

CVSS v3.1
4.2
MEDIUM
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
EPSS percentile
0
Exploit Prediction Scoring System · top 100% of all CVEs
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.

Timeline
Published 2026-08-13
Modified 2026-08-29

External references

Search for exposed instances

Shodan + Censys queries derived from NVD's CPE data. The vuln tag catches assets Shodan has explicitly linked to this CVE; the product / banner fingerprints find exposed instances even when the vuln tag was never applied (which is common).

More intel sources (5)

Known PoCs on GitHub (8)

We haven't classified any articles referencing CVE-2026-14681 yet. The external references above still apply.