Incorrect ownership assignment in PostgreSQL ALTER TABLE ALTER TYPE command reassigns ownership of dependent statistics objects to the current user. This wrongly allows the table owner to run DROP STATISTICS and ALTER STATISTICS via this improper ownership. It wrongly denies those commands to the prior statistics object owner. DROP TABLE remains able to remove statistics objects, so this exploit achieves nothing in many ownership arrangements. Versions before PostgreSQL 18.5, 17.11, 16.15, 15.19, and 14.24 are affected.
CVE-2026-6469
Score 3.8 from GitHub Security Advisory (severity: LOW) published 2026-08-13. a secondary CVSS source baseline 3.8; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 3.8
- EG Score
- 3.8(high)
- EG Risk
- 17(Track)EG Risk 17/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 computedSeverity38% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 25%
- KEV
- Not listed
Published
August 13, 2026
Last Modified
August 19, 2026
References (1)
- f86ef6dc-4d3a-42ad-8f28-e6d5547a5007https://www.postgresql.org/support/security/CVE-2026-6469/
Vendor Advisories for CVE-2026-6469(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 14× in last 7d / 21× 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.
- 2026-08-20 22:56 UTCEPSS rescore
- 2026-08-19 17:04 UTCEPSS rescore
- 2026-08-19 15:04 UTCGHSA enrichment
- 2026-08-18 15:29 UTCEG score recompute
- 2026-08-18 15:29 UTCGHSA enrichment
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-18 13:49 UTCEPSS rescore
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 11:35 UTCEG score recompute
- 2026-08-16 11:35 UTCGHSA enrichment
- 2026-08-16 02:15 UTCEPSS rescore
- 2026-08-15 01:31 UTCEPSS rescore
- 2026-08-13 16:29 UTCEG score recompute
- 2026-08-13 16:29 UTCGHSA enrichment
- 2026-08-13 16:01 UTCEG score recompute
- 2026-08-13 16:01 UTCGHSA enrichment
- 2026-08-13 13:35 UTCEG score recompute
- 2026-08-13 13:17 UTCEG score recompute
- 2026-08-13 13:16 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-6469?
When was CVE-2026-6469 disclosed?
Is CVE-2026-6469 actively exploited?
What is the CVSS score of CVE-2026-6469?
How do I remediate CVE-2026-6469?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-6469
Is Your Infrastructure Affected by CVE-2026-6469?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.