CVE-2026-6470

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

Score 4.3 from GitHub Security Advisory published 2026-08-13. A secondary CVSS source baseline 4.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 4 sources updated this week
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

Missing authorization in PostgreSQL DDL commands allows an object creator to achieve denial of service against ALTER and DROP of the type, via creating a dependency on the type. Many DDL operations did check the privilege, but assigning a range subtype and referencing the type from an SQL expression did not. Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
19
EG Risk 19/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
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
23rd
KEV
Not listed

CISA SSVCTrack at every mission impact level.

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

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (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-6470: PostgreSQL fails to check type USAGE privilege

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

Vendor Advisories for CVE-2026-6470(2)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntupostgresql-server-dev-18 (18.6-0ubuntu0.26.04.1) @ resolute2026-10-04ubuntu

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

(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 17× in last 7d / 95× 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 178 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-6470?
CVE-2026-6470 is a medium vulnerability published on August 13, 2026. Missing authorization in PostgreSQL DDL commands allows an object creator to achieve denial of service against ALTER and DROP of the type, via creating a dependency on the type. Many DDL operations did check the privilege, but assigning a range subtype and referencing the type from an SQL…
When was CVE-2026-6470 disclosed?
CVE-2026-6470 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-6470 actively exploited?
CVE-2026-6470 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (23rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-6470?
CVE-2026-6470 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-6470?
A fix for CVE-2026-6470 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-6470 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-6470

Explore →

Is Your Infrastructure Affected by CVE-2026-6470?

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