CVE-2026-6469: Incorrect Ownership Assignment in PostgreSQL
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.6, 17.11, 16.15, 15.19, and 14.24 are affected.
AI Analysis
Technical Summary
The vulnerability arises from incorrect ownership assignment in PostgreSQL's ALTER TABLE ALTER TYPE command. When this command is executed, ownership of dependent statistics objects is reassigned to the current user rather than preserving the original ownership. This misassignment allows the table owner to execute DROP STATISTICS and ALTER STATISTICS commands on these objects, which should normally be restricted to the original statistics object owner. Despite this, the DROP TABLE command can still remove statistics objects, which mitigates the potential impact in many ownership configurations. The issue affects PostgreSQL versions prior to 14.24, 15.19, 16.15, 17.11, and 18.5.
Potential Impact
The vulnerability allows improper reassignment of ownership of statistics objects, enabling the table owner to run DROP STATISTICS and ALTER STATISTICS commands that should be restricted. This could lead to unauthorized modification or removal of statistics objects. However, since DROP TABLE can still remove statistics objects regardless of ownership, the exploit's practical impact is limited in many scenarios. There is no confidentiality or availability impact reported, and no known exploits in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround is indicated in the provided data. Users should monitor PostgreSQL vendor advisories for updates and apply patches when available. Until then, be aware of the ownership reassignment behavior when using ALTER TABLE ALTER TYPE and consider restricting privileges accordingly.
CVE-2026-6469: Incorrect Ownership Assignment in PostgreSQL
Description
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.6, 17.11, 16.15, 15.19, and 14.24 are affected.
CVSS v3.1
Score 3.8low
Affected software
PostgreSQL
pkg:deb/postgresql/postgresqlRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises from incorrect ownership assignment in PostgreSQL's ALTER TABLE ALTER TYPE command. When this command is executed, ownership of dependent statistics objects is reassigned to the current user rather than preserving the original ownership. This misassignment allows the table owner to execute DROP STATISTICS and ALTER STATISTICS commands on these objects, which should normally be restricted to the original statistics object owner. Despite this, the DROP TABLE command can still remove statistics objects, which mitigates the potential impact in many ownership configurations. The issue affects PostgreSQL versions prior to 14.24, 15.19, 16.15, 17.11, and 18.5.
Potential Impact
The vulnerability allows improper reassignment of ownership of statistics objects, enabling the table owner to run DROP STATISTICS and ALTER STATISTICS commands that should be restricted. This could lead to unauthorized modification or removal of statistics objects. However, since DROP TABLE can still remove statistics objects regardless of ownership, the exploit's practical impact is limited in many scenarios. There is no confidentiality or availability impact reported, and no known exploits in the wild.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround is indicated in the provided data. Users should monitor PostgreSQL vendor advisories for updates and apply patches when available. Until then, be aware of the ownership reassignment behavior when using ALTER TABLE ALTER TYPE and consider restricting privileges accordingly.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- PostgreSQL
- Date Reserved
- 2026-04-17T00:21:37.212Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6a7dc619bf8831d5393e5416
Added to database: 08/13/2026, 13:26:49 UTC
Last enriched: 08/13/2026, 13:43:27 UTC
Last updated: 09/27/2026, 01:47:44 UTC
Views: 49
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.