CVE-2026-61817

Published: Set 18, 2026 Last Modified: Set 24, 2026
ExploitDB:
Other exploit source:
Google Dorks:
HIGH 8,5
Attack Vector: network
Attack Complexity: high
Privileges Required: low
User Interaction: none
Scope: changed
Confidentiality: high
Integrity: high
Availability: high

Description

AI Translation Available

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.

89

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Stable
Common Consequences
Security Scopes Affected:
Confidentiality Integrity Availability Authentication Access Control
Potential Impacts:
Execute Unauthorized Code Or Commands Read Application Data Gain Privileges Or Assume Identity Bypass Protection Mechanism Modify Application Data
Applicable Platforms
Languages: Not Language-Specific, SQL
Technologies: Database Server
View CWE Details
https://github.com/pgpartman/pg_partman/commit/ba9405542acf24dd881845b935cab8b1…
https://github.com/pgpartman/pg_partman/releases/tag/v5.5.0
https://github.com/pgpartman/pg_partman/security/advisories/GHSA-gmw2-52wc-258g