CVE-2026-14681

MEDIUMPre-NVD 4.24.2—
EchelonGraph scoreMEDIUM confidence

Score 4.2 from GitHub Security Advisory published 2026-08-13. a secondary CVSS source baseline 4.2; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.2EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.2Exploit: None knownExposed: 0

A fix is available — apply it.

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 v3
4.2
EG Score
4.2(medium)
EG Risk
19(Track)
EG Risk 19/100SSVC: Track

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 computed
Severity42% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
0%
KEV
Not listed

Published

August 13, 2026

Last Modified

August 29, 2026

Advisory Details (1)

Auto-updated Aug 13, 2026
No patch confirmed yet.
generic

PostgreSQL: 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 / EcosystemFixed in / PatchReleasedSource
ubuntupostgresql-server-dev-18 (18.6-0ubuntu0.26.04.1) @ resolute2026-09-19ubuntu

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)
PackageVulnerable rangeFixed inDependents
postgresql17—17.11-r0—
postgresql18—18.5-r0—
Alpine:v3.24(2)
PackageVulnerable rangeFixed inDependents
postgresql17—17.11-r0—
postgresql18—18.5-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
postgresql17—17.11-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
postgresql17—17.11-r0—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
postgresql-1717.10-0+deb13u1 ... 17.9-0+deb13u1 (7 versions)17.11-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
postgresql-1818.0-1 ... 18~~devel.20250502-1 (20 versions)18.6-1—

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 17× in last 7d / 75× 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.

  1. 2026-09-19 07:01 UTCVendor advisory
  2. 2026-09-19 07:01 UTCGHSA enrichment
  3. 2026-09-18 06:55 UTCVendor advisory
  4. 2026-09-18 06:55 UTCGHSA enrichment
  5. 2026-09-17 06:57 UTCEG score recompute
  6. 2026-09-17 06:57 UTCVendor advisory
  7. 2026-09-17 06:57 UTCGHSA enrichment
  8. 2026-09-16 14:07 UTCEPSS rescore
  9. 2026-09-16 06:20 UTCVendor advisory
  10. 2026-09-16 06:20 UTCGHSA enrichment
  11. 2026-09-15 06:22 UTCVendor advisory
  12. 2026-09-15 06:22 UTCGHSA enrichment
  13. 2026-09-14 04:57 UTCVendor advisory
  14. 2026-09-14 04:57 UTCGHSA enrichment
  15. 2026-09-13 05:00 UTCEG score recompute
  16. 2026-09-13 05:00 UTCVendor advisory
  17. 2026-09-13 05:00 UTCGHSA enrichment
  18. 2026-09-12 05:02 UTCEG score recompute
  19. 2026-09-12 05:02 UTCVendor advisory
  20. 2026-09-12 05:02 UTCGHSA enrichment
  21. 2026-09-11 14:52 UTCEPSS rescore
  22. 2026-09-11 05:04 UTCVendor advisory
  23. 2026-09-11 05:04 UTCGHSA enrichment
  24. 2026-09-10 05:06 UTCVendor advisory
  25. 2026-09-10 05:06 UTCGHSA enrichment
Show 73 more
  1. 2026-09-09 05:05 UTCVendor advisory
  2. 2026-09-09 05:05 UTCGHSA enrichment
  3. 2026-09-08 01:18 UTCVendor advisory
  4. 2026-09-08 01:18 UTCGHSA enrichment
  5. 2026-09-07 01:21 UTCGHSA enrichment
  6. 2026-09-06 01:23 UTCEG score recompute
  7. 2026-09-06 01:23 UTCVendor advisory
  8. 2026-09-06 01:23 UTCGHSA enrichment
  9. 2026-09-05 01:09 UTCGHSA enrichment
  10. 2026-09-04 01:09 UTCGHSA enrichment
  11. 2026-09-02 23:20 UTCVendor advisory
  12. 2026-09-02 23:20 UTCGHSA enrichment
  13. 2026-09-01 23:20 UTCVendor advisory
  14. 2026-09-01 23:20 UTCGHSA enrichment
  15. 2026-08-31 23:22 UTCVendor advisory
  16. 2026-08-31 23:22 UTCGHSA enrichment
  17. 2026-08-30 23:24 UTCVendor advisory
  18. 2026-08-30 23:24 UTCGHSA enrichment
  19. 2026-08-29 23:26 UTCEG score recompute
  20. 2026-08-29 23:26 UTCVendor advisory
  21. 2026-08-29 23:26 UTCGHSA enrichment
  22. 2026-08-29 23:14 UTCEG score recompute
  23. 2026-08-29 23:14 UTCVendor advisory
  24. 2026-08-29 23:14 UTCGHSA enrichment
  25. 2026-08-29 08:15 UTCEG score recompute
  26. 2026-08-29 08:15 UTCVendor advisory
  27. 2026-08-29 08:15 UTCGHSA enrichment
  28. 2026-08-28 21:41 UTCEPSS rescore
  29. 2026-08-28 01:00 UTCVendor advisory
  30. 2026-08-28 01:00 UTCGHSA enrichment
  31. 2026-08-27 01:02 UTCVendor advisory
  32. 2026-08-27 01:02 UTCGHSA enrichment
  33. 2026-08-26 01:04 UTCEG score recompute
  34. 2026-08-26 01:04 UTCGHSA enrichment
  35. 2026-08-25 13:48 UTCEPSS rescore
  36. 2026-08-25 01:07 UTCEG score recompute
  37. 2026-08-25 01:07 UTCVendor advisory
  38. 2026-08-25 01:06 UTCGHSA enrichment
  39. 2026-08-24 01:09 UTCVendor advisory
  40. 2026-08-24 01:09 UTCGHSA enrichment
  41. 2026-08-23 01:11 UTCEG score recompute
  42. 2026-08-23 01:11 UTCVendor advisory
  43. 2026-08-23 01:11 UTCGHSA enrichment
  44. 2026-08-23 00:19 UTCEPSS rescore
  45. 2026-08-22 01:13 UTCVendor advisory
  46. 2026-08-22 01:13 UTCGHSA enrichment
  47. 2026-08-21 01:15 UTCEG score recompute
  48. 2026-08-21 01:15 UTCVendor advisory
  49. 2026-08-21 01:15 UTCGHSA enrichment
  50. 2026-08-20 22:55 UTCEPSS rescore
  51. 2026-08-20 01:18 UTCEG score recompute
  52. 2026-08-20 01:18 UTCGHSA enrichment
  53. 2026-08-19 17:03 UTCEPSS rescore
  54. 2026-08-19 01:20 UTCGHSA enrichment
  55. 2026-08-18 15:33 UTCEG score recompute
  56. 2026-08-18 15:33 UTCGHSA enrichment
  57. 2026-08-18 13:48 UTCEPSS rescore
  58. 2026-08-17 16:29 UTCGHSA enrichment
  59. 2026-08-16 16:30 UTCEG score recompute
  60. 2026-08-16 16:30 UTCGHSA enrichment
  61. 2026-08-16 14:56 UTCEPSS rescore
  62. 2026-08-16 02:14 UTCEPSS rescore
  63. 2026-08-15 16:33 UTCEG score recompute
  64. 2026-08-15 16:33 UTCGHSA enrichment
  65. 2026-08-15 01:30 UTCEPSS rescore
  66. 2026-08-14 16:35 UTCGHSA enrichment
  67. 2026-08-13 16:29 UTCEG score recompute
  68. 2026-08-13 16:29 UTCGHSA enrichment
  69. 2026-08-13 16:02 UTCEG score recompute
  70. 2026-08-13 16:02 UTCGHSA enrichment
  71. 2026-08-13 13:35 UTCEG score recompute
  72. 2026-08-13 13:17 UTCEG score recompute
  73. 2026-08-13 13:16 UTCMITRE cvelistV5first tracked

Frequently asked(5)

What is CVE-2026-14681?
CVE-2026-14681 is a medium vulnerability published on August 13, 2026. Improper enforcement of message integrity in PostgreSQL GSSAPI support allows a user to negotiate GSSAPI contrary to pghba.conf rules, via initial direct TLS connection. Despite a pghba.conf that appears to require GSSAPI, the connection may exchange data over TLS encryption alone. If the TLS…
When was CVE-2026-14681 disclosed?
CVE-2026-14681 was first published in the National Vulnerability Database on August 13, 2026, with the most recent update on August 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-14681 actively exploited?
CVE-2026-14681 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 100.0% of all scored CVEs.
What is the CVSS score of CVE-2026-14681?
CVE-2026-14681 has a CVSS v3 base score of 4.2 (NVD).
How do I remediate CVE-2026-14681?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14681, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-14681

Explore →

Is Your Infrastructure Affected by CVE-2026-14681?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs