Improper Check or Handling of Exceptional Conditions Affecting pg-partman package, versions <5.5.0-1
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-ECHOLATEST-PGPARTMAN-19946234
- published19 Sept 2026
- disclosed18 Sept 2026
Introduced: 18 Sep 2026
NewCVE-2026-61822 (opens in a new tab)How to fix?
Upgrade Echo:latest pg-partman to version 5.5.0-1 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream pg-partman package and not the pg-partman package as distributed by Echo.
See How to fix? for Echo:latest relevant fixed versions and status.
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.