CVE-2026-61822: CWE-703: Improper Check or Handling of Exceptional Conditions in pgpartman pg_partman
pg_partman is a PostgreSQL extension that manages partitioned tables by time or ID. Prior to 5.5.0, run_maintenance() handles exceptions outside the loop that processes rows from part_config, so an exception for one partition set immediately terminates the loop and skips every later set. A role with partman_user access can insert or update a row that reliably fails and assign it a low maintenance_order value so it is processed before legitimate rows. Repeated maintenance ticks then abort before legitimate partition sets are maintained, causing database-wide loss of automated partition maintenance. This issue is fixed in version 5.5.0.
AI Analysis
Technical Summary
The pg_partman extension for PostgreSQL manages partitioned tables by time or ID. Before version 5.5.0, the run_maintenance() function handles exceptions outside the loop that processes partition configurations. If an exception occurs for one partition set, the loop terminates immediately, skipping subsequent partition sets. A user with partman_user privileges can insert or update a row that causes a reliable failure and assign it a low maintenance_order value, ensuring it is processed before legitimate rows. This causes repeated maintenance ticks to abort prematurely, resulting in a database-wide loss of automated partition maintenance. The vulnerability is addressed in pg_partman version 5.5.0.
Potential Impact
An attacker with partman_user role can cause the automated partition maintenance process to abort repeatedly by triggering an exception early in the maintenance loop. This results in legitimate partition sets not being maintained, potentially leading to degraded database performance or operational issues due to lack of partition maintenance. There is no direct confidentiality or integrity impact reported, but availability of automated maintenance is affected.
Mitigation Recommendations
Upgrade pg_partman to version 5.5.0 or later where this issue is fixed. No other mitigation is indicated by the vendor advisory.
CVE-2026-61822: CWE-703: Improper Check or Handling of Exceptional Conditions in pgpartman pg_partman
Description
pg_partman is a PostgreSQL extension that manages partitioned tables by time or ID. Prior to 5.5.0, run_maintenance() handles exceptions outside the loop that processes rows from part_config, so an exception for one partition set immediately terminates the loop and skips every later set. A role with partman_user access can insert or update a row that reliably fails and assign it a low maintenance_order value so it is processed before legitimate rows. Repeated maintenance ticks then abort before legitimate partition sets are maintained, causing database-wide loss of automated partition maintenance. This issue is fixed in version 5.5.0.
CVSS v3.1
Score 6.5medium
Affected software
pgpartman
pg_partman
pkg:github/pgpartman/pg_partmanRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The pg_partman extension for PostgreSQL manages partitioned tables by time or ID. Before version 5.5.0, the run_maintenance() function handles exceptions outside the loop that processes partition configurations. If an exception occurs for one partition set, the loop terminates immediately, skipping subsequent partition sets. A user with partman_user privileges can insert or update a row that causes a reliable failure and assign it a low maintenance_order value, ensuring it is processed before legitimate rows. This causes repeated maintenance ticks to abort prematurely, resulting in a database-wide loss of automated partition maintenance. The vulnerability is addressed in pg_partman version 5.5.0.
Potential Impact
An attacker with partman_user role can cause the automated partition maintenance process to abort repeatedly by triggering an exception early in the maintenance loop. This results in legitimate partition sets not being maintained, potentially leading to degraded database performance or operational issues due to lack of partition maintenance. There is no direct confidentiality or integrity impact reported, but availability of automated maintenance is affected.
Mitigation Recommendations
Upgrade pg_partman to version 5.5.0 or later where this issue is fixed. No other mitigation is indicated by the vendor advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-07-10T20:17:57.992Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 6aad98c355bf5e2cf57b8898
Added to database: 09/18/2026, 20:02:11 UTC
Last enriched: 09/18/2026, 20:17:15 UTC
Last updated: 09/19/2026, 02:58:38 UTC
Views: 8
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.
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.