CVE-2026-6637

HIGHNVD 8.88.8
EchelonGraph scoreMEDIUM confidence

Score 8.8 from GitHub Security Advisory (severity: HIGH) published 2026-05-14. NVD baseline CVSS 8.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.8Exploit: NoneExposed: 0

A fix is available — apply it.

Stack buffer overflow in PostgreSQL module "refint" allows an unprivileged database user to execute arbitrary code as the operating system user running the database. A distinct attack is possible if the application declares a user-controlled column as a "refint" cascade primary key and facilitates user-controlled updates to that column. In that case, a SQL injection allows a primary key update value provider to execute arbitrary SQL as the database user performing the primary key update. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

CVSS v3
8.8
EG Score
8.8(medium)
EPSS
29.9%
KEV
Not listed

Published

May 14, 2026

Last Modified

May 18, 2026

Advisory Details (1)

Auto-updated May 14, 2026
No patch confirmed yet.
generic

PostgreSQL: CVE-2026-6637: PostgreSQL refint allows stack buffer overflow and SQL injection

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

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupostgresql-server-dev-18 (18.4-0ubuntu0.26.04.1) @ resolute2026-06-29ubuntu

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.

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 10× in last 7d / 78× 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 194 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-6637?
CVE-2026-6637 is a high vulnerability published on May 14, 2026. Stack buffer overflow in PostgreSQL module "refint" allows an unprivileged database user to execute arbitrary code as the operating system user running the database. A distinct attack is possible if the application declares a user-controlled column as a "refint" cascade primary key and facilitates…
When was CVE-2026-6637 disclosed?
CVE-2026-6637 was first published in the National Vulnerability Database on May 14, 2026, with the most recent update on May 18, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6637 actively exploited?
CVE-2026-6637 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 29.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-6637?
CVE-2026-6637 has a CVSS v3 base score of 8.8 (NVD).
How do I remediate CVE-2026-6637?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6637, 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

Explore the affected products and dependency analysis for CVE-2026-6637

Explore →

Is Your Infrastructure Affected by CVE-2026-6637?

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