CVE-2026-14681

MEDIUMPre-NVD 4.24.2—
EchelonGraph scoreHIGH 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.5 and 17.11 are affected. Versions before PostgreSQL 17 are unaffected.

CVSS v3
4.2
EG Score
4.2(high)
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 19, 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-08-21ubuntu

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.

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 20× in last 7d / 27× 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-08-21 01:15 UTCEG score recompute
  2. 2026-08-21 01:15 UTCVendor advisory
  3. 2026-08-21 01:15 UTCGHSA enrichment
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 01:18 UTCEG score recompute
  6. 2026-08-20 01:18 UTCGHSA enrichment
  7. 2026-08-19 17:03 UTCEPSS rescore
  8. 2026-08-19 01:20 UTCGHSA enrichment
  9. 2026-08-18 15:33 UTCEG score recompute
  10. 2026-08-18 15:33 UTCGHSA enrichment
  11. 2026-08-18 13:48 UTCEPSS rescore
  12. 2026-08-17 16:29 UTCGHSA enrichment
  13. 2026-08-16 16:30 UTCEG score recompute
  14. 2026-08-16 16:30 UTCGHSA enrichment
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 02:14 UTCEPSS rescore
  17. 2026-08-15 16:33 UTCEG score recompute
  18. 2026-08-15 16:33 UTCGHSA enrichment
  19. 2026-08-15 01:30 UTCEPSS rescore
  20. 2026-08-14 16:35 UTCGHSA enrichment
  21. 2026-08-13 16:29 UTCEG score recompute
  22. 2026-08-13 16:29 UTCGHSA enrichment
  23. 2026-08-13 16:02 UTCEG score recompute
  24. 2026-08-13 16:02 UTCGHSA enrichment
  25. 2026-08-13 13:35 UTCEG score recompute
Show 2 more
  1. 2026-08-13 13:17 UTCEG score recompute
  2. 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 19, 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 99.8% 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

Explore the affected products and dependency analysis for 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