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.2%CVSS: 4.3Exploit: None knownExposed services: Not assessed

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.3MEDIUMmedium confidence
EG Risk
19
EG 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 computed
Severity43% × 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.2%
EPSS %ILE
8th
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, 2026
Patch available.
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(2)

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 / EcosystemFix (by version range) / PatchReleasedSource
ubuntupostgresql-server-dev-18 (18.6-0ubuntu0.26.04.1) @ resolute2026-10-04ubuntu

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 rangeFix by version rangeDependents
postgresql16—
  • every version up to 16.15-r0: fixed in 16.15-r0
—
postgresql17—
  • every version up to 17.11-r0: fixed in 17.11-r0
—
Alpine:v3.22(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql16—
  • every version up to 16.15-r0: fixed in 16.15-r0
—
postgresql17—
  • every version up to 17.11-r0: fixed in 17.11-r0
—
Alpine:v3.23(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql17—
  • every version up to 17.11-r0: fixed in 17.11-r0
—
postgresql18—
  • every version up to 18.5-r0: fixed in 18.5-r0
—
Alpine:v3.24(2)
PackageVulnerable rangeFix by version rangeDependents
postgresql17—
  • every version up to 17.11-r0: fixed in 17.11-r0
—
postgresql18—
  • every version up to 18.5-r0: fixed in 18.5-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1515.10-0+deb12u1 ... 15.9-0+deb12u1 (21 versions)
  • every version up to 15.19-0+deb12u1: fixed in 15.19-0+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1717.10-0+deb13u1 ... 17.9-0+deb13u1 (7 versions)
  • every version up to 17.11-0+deb13u1: fixed in 17.11-0+deb13u1
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
postgresql-1818.0-1 ... 18~~devel.20250502-1 (20 versions)
  • every version up to 18.6-1: fixed in 18.6-1
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 16× in last 7d / 94× 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 177 total refreshes for this CVE.

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

Related CVEs(same product + same vendor + same CWE)

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 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.2% probability of exploitation in the next 30 days (8th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-14678?
CVE-2026-14678 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-14678?
A fix for CVE-2026-14678 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-14678 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs