CVE-2026-14680

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.

Type confusion with PostgreSQL "internal" data type arguments allows any user to execute arbitrary code as the operating system user running the database, via calls to functions with that argument type. Type "internal" represents a class of mutually-incompatible data structures not intended for access from SQL. The system intended to prevent such function calls, but this prevention had gaps. 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
36%
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-14680: PostgreSQL type confusion via "internal" arguments

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

Vendor Advisories for CVE-2026-14680(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-14 (14.24-0ubuntu0.22.04.1) @ jammy2026-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 36× in last 7d / 159× 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 196 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-14680?
CVE-2026-14680 is a high vulnerability published on August 13, 2026. Type confusion with PostgreSQL "internal" data type arguments allows any user to execute arbitrary code as the operating system user running the database, via calls to functions with that argument type. Type "internal" represents a class of mutually-incompatible data structures not intended for…
When was CVE-2026-14680 disclosed?
CVE-2026-14680 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-14680 actively exploited?
CVE-2026-14680 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.8% of all scored CVEs.
What is the CVSS score of CVE-2026-14680?
CVE-2026-14680 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-14680?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-14680, 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-14680

Explore →

Is Your Infrastructure Affected by CVE-2026-14680?

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

Start Free Scan →Browse All CVEs