No advisories yet.
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
| Link | Providers |
|---|---|
| https://www.postgresql.org/support/security/CVE-2026-14681/ |
|
Thu, 13 Aug 2026 16:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 13 Aug 2026 15:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Postgresql
Postgresql postgresql |
|
| Vendors & Products |
Postgresql
Postgresql postgresql |
Thu, 13 Aug 2026 13:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| 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.5 and 17.11 are affected. Versions before PostgreSQL 17 are unaffected. | |
| Title | PostgreSQL improper enforcement of GSSAPI encryption when coupled with SSL | |
| Weaknesses | CWE-924 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: PostgreSQL
Published:
Updated: 2026-08-13T15:37:34.410Z
Reserved: 2026-07-03T20:28:19.093Z
Link: CVE-2026-14681
Updated: 2026-08-13T15:37:29.370Z
Status : Received
Published: 2026-08-13T13:17:45.523
Modified: 2026-08-13T16:17:57.253
Link: CVE-2026-14681
No data.
OpenCVE Enrichment
Updated: 2026-08-13T14:45:03Z