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%CVSS: 8.8Exploit: None knownExposed: 0

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.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-14670: PostgreSQL plperl tied object heap buffer overflow executes arbitrary code

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

Vendor Advisories for CVE-2026-14670(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-20ubuntu
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 32× in last 7d / 163× 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 205 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 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-14670 actively exploited?
CVE-2026-14670 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 62.7% of all scored CVEs.
What is the CVSS score of CVE-2026-14670?
CVE-2026-14670 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-14670?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14670, 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-14670

Explore →

Is Your Infrastructure Affected by CVE-2026-14670?

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

Start Free Scan →Browse All CVEs