CVE-2026-61821
8.5pgpartman · pg_partman
A privilege escalation vulnerability in the pg_partman PostgreSQL extension allows authenticated users to move tables between schemas by exploiting improper authorization checks in background tasks.
Executive summary
A critical privilege escalation vulnerability in pg_partman allows authenticated users to bypass authorization checks and unauthorizedly relocate partitioned tables, potentially granting access to sensitive data.
Vulnerability
This is a missing authorization vulnerability (CWE-862) occurring within the drop_partition_id and drop_partition_time functions. A user with partman_user access can force a background worker, which operates with superuser privileges, to move child tables into unauthorized schemas.
Business impact
The ability to relocate tables bypasses standard database access controls, which may lead to unauthorized data exposure or the corruption of data management workflows. With a CVSS score of 8.5, this high severity flaw poses a significant risk to database integrity and confidentiality. Organizations relying on this extension for automated partitioning should prioritize this fix to prevent lateral movement or data exfiltration by lower privileged accounts.
Remediation
Immediate Action: Update pg_partman to version 5.5.0 or later to ensure that authorization checks are correctly enforced during schema relocation.
Proactive Monitoring: Review database audit logs for unusual ALTER TABLE operations or unexpected schema changes involving partitioned tables.
Compensating Controls: Restrict the partman_user role to only trusted accounts and ensure that database background workers are configured with the minimum necessary privileges to perform their tasks.
Exploitation status
Public Exploit Available: No
Analyst recommendation
The vulnerability represents a significant breach of the principle of least privilege within the PostgreSQL environment. Given the high severity and the potential for unauthorized data relocation, administrators must apply the 5.5.0 patch immediately. Testing the update in a staging environment is advised to ensure compatibility with existing partition management configurations before deploying to production.
More pgpartman CVEs
History
- Disclosed CVE record published
- Collected by CVE Brief via github
- Analyst report written
- Published in the daily brief high section