CVE-2026-14668

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — Patch released this week
8.1EG
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.1Exploit: None knownExposed: 0

A fix is available — apply it.

Type confusion regarding input of PostgreSQL ctid data type selectivity estimator allows an object creator to view a calculation derived from the value of an arbitrary 4-byte span of memory, via a chosen non-ctid input. While the calculation loses precision, substantial memory value recovery appears possible. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

CVSS v3
8.1
EG Score
8.1(medium)
EG Risk
37(Track)
EG Risk 37/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
Severity81% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
27%
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-14668: PostgreSQL ctid type confusion in selectivity estimator discloses derivative of arbitrary read

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

Vendor Advisories for CVE-2026-14668(1)

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

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupostgresql-server-dev-18 (18.6-0ubuntu0.26.04.1) @ resolute2026-09-19ubuntu
redhatpostgresql:18-9080020260914093252.rhel92026-09-16redhat
redhatpostgresql:16-9080020260907191505.rhel92026-09-15redhat
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

(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

(5)

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 42× in last 7d / 173× 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 208 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-14668?
CVE-2026-14668 is a high vulnerability published on August 13, 2026. Type confusion regarding input of PostgreSQL ctid data type selectivity estimator allows an object creator to view a calculation derived from the value of an arbitrary 4-byte span of memory, via a chosen non-ctid input. While the calculation loses precision, substantial memory value recovery…
When was CVE-2026-14668 disclosed?
CVE-2026-14668 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-14668 actively exploited?
CVE-2026-14668 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 73.2% of all scored CVEs.
What is the CVSS score of CVE-2026-14668?
CVE-2026-14668 has a CVSS v3 base score of 8.1 (NVD).
How do I remediate CVE-2026-14668?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14668, 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-14668

Explore →

Is Your Infrastructure Affected by CVE-2026-14668?

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

Start Free Scan →Browse All CVEs