CVE-2026-14678

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

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

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

A fix is available — apply it.

Buffer over-read in PostgreSQL pg_trgm index picksplit function reads past end of a heap buffer. This might allow a table maintainer to infer limited memory values, via the lossy signal of index split choices. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

CVSS v3
4.3
EG Score
4.3(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
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
10%
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-14678: PostgreSQL pg_trgm picksplit reads past end of buffer

https://www.postgresql.org/support/security/CVE-2026-14678/

Vendor Advisories for CVE-2026-14678(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

(11 across 7 ecosystems)
Alpine:v3.21(2)
PackageVulnerable rangeFixed inDependents
postgresql16—16.15-r0—
postgresql17—17.11-r0—
Alpine:v3.22(2)
PackageVulnerable rangeFixed inDependents
postgresql16—16.15-r0—
postgresql17—17.11-r0—
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—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
postgresql-1515.10-0+deb12u1 ... 15.9-0+deb12u1 (21 versions)15.19-0+deb12u1—
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

(2)

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 24× in last 7d / 111× 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 134 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-14678?
CVE-2026-14678 is a medium vulnerability published on August 13, 2026. Buffer over-read in PostgreSQL pg_trgm index picksplit function reads past end of a heap buffer. This might allow a table maintainer to infer limited memory values, via the lossy signal of index split choices. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
When was CVE-2026-14678 disclosed?
CVE-2026-14678 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-14678 actively exploited?
CVE-2026-14678 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 90.5% of all scored CVEs.
What is the CVSS score of CVE-2026-14678?
CVE-2026-14678 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-14678?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14678, 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-14678

Explore →

Is Your Infrastructure Affected by CVE-2026-14678?

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

Start Free Scan →Browse All CVEs