CVE-2026-14670

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

A fix is available — apply it.

Heap buffer overflow in PostgreSQL plperl return of a tied hash allows the function owner to execute arbitrary code as the operating system user running the database, via a crafted function body. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

CVSS v3
8.8
EG Score
8.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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
Severity88% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at low or medium mission impact; Track* at high (mission-essential systems).
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.4%
EPSS %ILE
35th
KEV
Not listed

CISA SSVCTrack at low or medium mission impact; Track* at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (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-14670: PostgreSQL plperl tied object heap buffer overflow executes arbitrary code

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

Patch Availability(23)

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

(4)

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-14670?
CVE-2026-14670 is a high vulnerability published on August 13, 2026. Heap buffer overflow in PostgreSQL plperl return of a tied hash allows the function owner to execute arbitrary code as the operating system user running the database, via a crafted function body. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.
When was CVE-2026-14670 disclosed?
CVE-2026-14670 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-14670 actively exploited?
CVE-2026-14670 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (35th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-14670?
CVE-2026-14670 has a CVSS base score of 8.8 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-14670?
A fix for CVE-2026-14670 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-14670 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-14670

Explore →

Is Your Infrastructure Affected by CVE-2026-14670?

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