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.
CVE-2026-14681
Score 4.2 from GitHub Security Advisory published 2026-08-13. A secondary CVSS source baseline 4.2; sources differ by 0.0.
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 4.2
- EG Score
- 4.2MEDIUMmedium confidence
- EG Risk
- 19EG Risk 19/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity42% × 45%Exploitation0% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- <0.1%
- EPSS %ILE
- below the 1st
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
August 13, 2026
Last Modified
August 29, 2026
Advisory Details (1)
Auto-updated Aug 13, 2026PostgreSQL: CVE-2026-14681: PostgreSQL improper enforcement of GSSAPI encryption when coupled with SSL
https://www.postgresql.org/support/security/CVE-2026-14681/Vendor Advisories for CVE-2026-14681(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| ubuntu | postgresql-server-dev-18 (18.6-0ubuntu0.26.04.1) @ resolute | 2026-10-06 | ubuntu |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Affected Packages
(8 across 6 ecosystems)
Alpine:v3.23(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgresql17 | — |
| — |
| postgresql18 | — |
| — |
Alpine:v3.24(2)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgresql17 | — |
| — |
| postgresql18 | — |
| — |
Alpine:v3.21(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgresql17 | — |
| — |
Alpine:v3.22(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgresql17 | — |
| — |
Debian:13(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgresql-17 | 17.10-0+deb13u1 ... 17.9-0+deb13u1 (7 versions) |
| — |
Debian:14(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| postgresql-18 | 18.0-1 ... 18~~devel.20250502-1 (20 versions) |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
All Vendor Advisories
(1)
Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.
Data Freshness Timeline
(refreshed 10× in last 7d / 59× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 132 total refreshes for this CVE.
- 2026-10-09 20:06 UTCEPSS rescore
- 2026-10-08 17:11 UTCEPSS rescore
- 2026-10-07 23:47 UTCEPSS rescore
- 2026-10-06 15:17 UTCEPSS rescore
- 2026-10-06 13:53 UTCVendor advisory
- 2026-10-06 13:53 UTCGHSA enrichment
- 2026-10-04 22:24 UTCVendor advisory
- 2026-10-04 22:24 UTCGHSA enrichment
- 2026-10-03 19:52 UTCVendor advisory
- 2026-10-03 19:52 UTCGHSA enrichment
- 2026-10-02 08:05 UTCVendor advisory
- 2026-10-02 08:04 UTCGHSA enrichment
- 2026-09-30 21:50 UTCEG score recompute
- 2026-09-30 21:50 UTCVendor advisory
- 2026-09-30 21:50 UTCGHSA enrichment
- 2026-09-28 09:45 UTCVendor advisory
- 2026-09-28 09:45 UTCGHSA enrichment
- 2026-09-27 09:48 UTCEG score recompute
- 2026-09-27 09:48 UTCVendor advisory
- 2026-09-27 09:48 UTCGHSA enrichment
- 2026-09-25 10:02 UTCEG score recompute
- 2026-09-25 10:02 UTCVendor advisory
- 2026-09-25 10:02 UTCGHSA enrichment
- 2026-09-24 10:03 UTCEG score recompute
- 2026-09-24 10:03 UTCVendor advisory
Show 75 moreShow fewer
- 2026-09-24 10:03 UTCGHSA enrichment
- 2026-09-23 10:05 UTCVendor advisory
- 2026-09-23 10:05 UTCGHSA enrichment
- 2026-09-22 10:07 UTCVendor advisory
- 2026-09-22 10:07 UTCGHSA enrichment
- 2026-09-21 10:08 UTCVendor advisory
- 2026-09-21 10:08 UTCGHSA enrichment
- 2026-09-20 10:10 UTCVendor advisory
- 2026-09-20 10:10 UTCGHSA enrichment
- 2026-09-19 07:01 UTCVendor advisory
- 2026-09-19 07:01 UTCGHSA enrichment
- 2026-09-18 06:55 UTCVendor advisory
- 2026-09-18 06:55 UTCGHSA enrichment
- 2026-09-17 06:57 UTCEG score recompute
- 2026-09-17 06:57 UTCVendor advisory
- 2026-09-17 06:57 UTCGHSA enrichment
- 2026-09-16 14:07 UTCEPSS rescore
- 2026-09-16 06:20 UTCVendor advisory
- 2026-09-16 06:20 UTCGHSA enrichment
- 2026-09-15 06:22 UTCVendor advisory
- 2026-09-15 06:22 UTCGHSA enrichment
- 2026-09-14 04:57 UTCVendor advisory
- 2026-09-14 04:57 UTCGHSA enrichment
- 2026-09-13 05:00 UTCEG score recompute
- 2026-09-13 05:00 UTCVendor advisory
- 2026-09-13 05:00 UTCGHSA enrichment
- 2026-09-12 05:02 UTCEG score recompute
- 2026-09-12 05:02 UTCVendor advisory
- 2026-09-12 05:02 UTCGHSA enrichment
- 2026-09-11 14:52 UTCEPSS rescore
- 2026-09-11 05:04 UTCVendor advisory
- 2026-09-11 05:04 UTCGHSA enrichment
- 2026-09-10 05:06 UTCVendor advisory
- 2026-09-10 05:06 UTCGHSA enrichment
- 2026-09-09 05:05 UTCVendor advisory
- 2026-09-09 05:05 UTCGHSA enrichment
- 2026-09-08 01:18 UTCVendor advisory
- 2026-09-08 01:18 UTCGHSA enrichment
- 2026-09-07 01:21 UTCGHSA enrichment
- 2026-09-06 01:23 UTCEG score recompute
- 2026-09-06 01:23 UTCVendor advisory
- 2026-09-06 01:23 UTCGHSA enrichment
- 2026-09-05 01:09 UTCGHSA enrichment
- 2026-09-04 01:09 UTCGHSA enrichment
- 2026-09-02 23:20 UTCVendor advisory
- 2026-09-02 23:20 UTCGHSA enrichment
- 2026-09-01 23:20 UTCVendor advisory
- 2026-09-01 23:20 UTCGHSA enrichment
- 2026-08-31 23:22 UTCVendor advisory
- 2026-08-31 23:22 UTCGHSA enrichment
- 2026-08-30 23:24 UTCVendor advisory
- 2026-08-30 23:24 UTCGHSA enrichment
- 2026-08-29 23:26 UTCEG score recompute
- 2026-08-29 23:26 UTCVendor advisory
- 2026-08-29 23:26 UTCGHSA enrichment
- 2026-08-29 23:14 UTCEG score recompute
- 2026-08-29 23:14 UTCVendor advisory
- 2026-08-29 23:14 UTCGHSA enrichment
- 2026-08-29 08:15 UTCEG score recompute
- 2026-08-29 08:15 UTCVendor advisory
- 2026-08-29 08:15 UTCGHSA enrichment
- 2026-08-28 21:41 UTCEPSS rescore
- 2026-08-28 01:00 UTCVendor advisory
- 2026-08-28 01:00 UTCGHSA enrichment
- 2026-08-27 01:02 UTCVendor advisory
- 2026-08-27 01:02 UTCGHSA enrichment
- 2026-08-26 01:04 UTCEG score recompute
- 2026-08-26 01:04 UTCGHSA enrichment
- 2026-08-25 13:48 UTCEPSS rescore
- 2026-08-25 01:07 UTCEG score recompute
- 2026-08-25 01:07 UTCVendor advisory
- 2026-08-25 01:06 UTCGHSA enrichment
- 2026-08-24 01:09 UTCVendor advisory
- 2026-08-24 01:09 UTCGHSA enrichment
- 2026-08-23 01:11 UTCEG score recompute
Related CVEs(same product + same vendor + same CWE)
Same product
10 shownAlpine:v3.23:postgresql18
Same vendor
10 shownubuntu:USN-8653-1
Frequently asked(5)
What is CVE-2026-14681?
When was CVE-2026-14681 disclosed?
Is CVE-2026-14681 actively exploited?
What is the CVSS score of CVE-2026-14681?
How do I remediate CVE-2026-14681?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-14681
Is Your Infrastructure Affected by CVE-2026-14681?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.