CVE-2026-6472

MEDIUMNVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

Score 5.4 from GitHub Security Advisory published 2026-05-14. NVD baseline CVSS 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.4Exploit: None knownExposed: 0

A fix is available — apply it.

Missing authorization in PostgreSQL CREATE TYPE allows an object creator to hijack other queries that use search_path to find user-defined types, including extension-defined types. That is to say, the victim will execute arbitrary SQL functions of the attacker's choice. Versions before PostgreSQL 18.4, 17.10, 16.14, 15.18, and 14.23 are affected.

CVSS v3
5.4
EG Score
5.4(medium)
EG Risk
24(Track)
EG Risk 24/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
Severity54% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
5%
KEV
Not listed

Published

May 14, 2026

Last Modified

May 18, 2026

Advisory Details (1)

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

PostgreSQL: CVE-2026-6472: PostgreSQL CREATE TYPE does not check multirange schema CREATE privilege

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

Vendor Advisories for CVE-2026-6472(19)

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

Patch Availability(18)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupostgresql-server-dev-18 (18.4-0ubuntu0.26.04.1) @ resolute2026-08-23ubuntu
redhatrhui5/rhua-rhel9:17847950762026-07-23redhat
redhatpostgresql:15-9020020260625101129.rhel92026-06-30redhat
redhatpostgresql:15-9040020260616071806.rhel92026-06-30redhat
redhatpostgresql:15-9060020260622062902.rhel92026-06-29redhat
redhatpostgresql:16-8100020260530205218.489197e62026-06-23redhat
redhatpostgresql16-0:16.14-1.el10_22026-06-22redhat
redhatpostgresql18-0:18.4-1.el10_22026-06-22redhat
redhatpostgresql16-0:16.14-1.el10_02026-06-22redhat
redhatpostgresql:15-9080020260605124405.rhel92026-06-22redhat
redhatpostgresql:16-9040020260612132455.rhel92026-06-17redhat
redhatpostgresql:16-9060020260612084605.rhel92026-06-17redhat
redhatpostgresql:15-8080020260615085052.63b345852026-06-17redhat
redhatpostgresql:18-9080020260605125734.rhel92026-06-16redhat
redhatpostgresql:15-8100020260605152259.489197e62026-06-16redhat
redhatpostgresql:16-9080020260605131007.rhel92026-06-16redhat
redhatpostgresql18-main-18.4-0.1.hum12026-06-03redhat
redhatpostgresql17-main-17.10-0.1.hum12026-05-26redhat

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

(13 across 8 ecosystems)
Alpine:v3.20(2)
PackageVulnerable rangeFixed inDependents
postgresql15—15.18-r0—
postgresql16—16.14-r0—
Alpine:v3.21(2)
PackageVulnerable rangeFixed inDependents
postgresql16—16.14-r0—
postgresql17—17.10-r0—
Alpine:v3.22(2)
PackageVulnerable rangeFixed inDependents
postgresql16—16.14-r0—
postgresql17—17.10-r0—
Alpine:v3.23(2)
PackageVulnerable rangeFixed inDependents
postgresql17—17.10-r0—
postgresql18—18.4-r0—
Alpine:v3.24(2)
PackageVulnerable rangeFixed inDependents
postgresql17—17.10-r0—
postgresql18—18.4-r0—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
postgresql-1515.10-0+deb12u1 ... 15.9-0+deb12u1 (20 versions)15.18-0+deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
postgresql-1717.5-1 ... 17.9-0+deb13u1 (6 versions)17.10-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
postgresql-1818.0-1 ... 18~~devel.20250502-1 (19 versions)18.4-1—

Weakness Classification(1)

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 6× in last 7d / 67× 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 229 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-6472?
CVE-2026-6472 is a medium vulnerability published on May 14, 2026. Missing authorization in PostgreSQL CREATE TYPE allows an object creator to hijack other queries that use search_path to find user-defined types, including extension-defined types. That is to say, the victim will execute arbitrary SQL functions of the attacker's choice. Versions before PostgreSQL…
When was CVE-2026-6472 disclosed?
CVE-2026-6472 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-6472 actively exploited?
CVE-2026-6472 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 94.7% of all scored CVEs.
What is the CVSS score of CVE-2026-6472?
CVE-2026-6472 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-6472?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6472, 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-6472

Explore →

Is Your Infrastructure Affected by CVE-2026-6472?

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

Start Free Scan →Browse All CVEs