CVE-2026-14676

HIGHPre-NVD 8.88.8—
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-08-13. a secondary CVSS source baseline 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
8.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 8.8Exploit: None knownExposed: 0

A fix is available — apply it.

Heap buffer overflow in PostgreSQL pg_stat_statements allows the query author to execute arbitrary code as the operating system user running the database, via crafted queries containing array constants. Within major version 18, minor versions before PostgreSQL 18.6 are affected. Versions before PostgreSQL 18 are unaffected.

CVSS v3
8.8
EG Score
8.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
37%
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-14676: PostgreSQL pg_stat_statements heap buffer overflow executes arbitrary code

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

Vendor Advisories for CVE-2026-14676(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(3)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupostgresql-server-dev-18 (18.6-0ubuntu0.26.04.1) @ resolute2026-09-21ubuntu
redhatpostgresql:18-9080020260914093252.rhel92026-09-16redhat
redhatpostgresql18-0:18.6-1.el10_22026-09-14redhat

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

(9 across 5 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: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

(3)

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 33× in last 7d / 148× 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 187 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-14676?
CVE-2026-14676 is a high vulnerability published on August 13, 2026. Heap buffer overflow in PostgreSQL pgstatstatements allows the query author to execute arbitrary code as the operating system user running the database, via crafted queries containing array constants. Within major version 18, minor versions before PostgreSQL 18.6 are affected. Versions before…
When was CVE-2026-14676 disclosed?
CVE-2026-14676 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-14676 actively exploited?
CVE-2026-14676 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 63.5% of all scored CVEs.
What is the CVSS score of CVE-2026-14676?
CVE-2026-14676 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-14676?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14676, 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-14676

Explore →

Is Your Infrastructure Affected by CVE-2026-14676?

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

Start Free Scan →Browse All CVEs