SQL Injection 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-19946229
- published19 Sept 2026
- disclosed18 Sept 2026
Introduced: 18 Sep 2026
NewCVE-2026-61817 (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(), show_partitions(), show_partition_info(), undo_partition(), and partition_data_time() interpolate the writable part_config.time_dncoder text value without identifier quoting into dynamic SQL. A role with the documented partman_user privileges can store SQL rather than a decoder function name. When an affected operation later uses the poisoned value, including pg_partman_bgw maintenance for a text- or UUID-keyed set, the SQL executes with the operation's privileges, which can be the default PostgreSQL superuser background-worker role. The persistent row can restore elevated access on later ticks, and successful exploitation can permit database-wide compromise and operating-system command execution as the PostgreSQL service account. This issue is fixed in version 5.5.0.