Quick answers
- Is CVE-2026-61822 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-61822 being exploited in the wild.
- How severe is CVE-2026-61822?
- Medium severity, with a CVSS score of 6.5, published 18 September 2026.
- Which products and versions are affected?
- Pgpartman Pg Partman before 5.5.0.
- Is there a fix for CVE-2026-61822?
- A patch was published on 2026-07-22: version 5.5.0 released Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-61822 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-61822?
- Check whether you run Pgpartman Pg Partman at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in the run_maintenance() function, which processes multiple partition sets from the part_config table in a loop. Exception handling was placed outside the loop, so any exception immediately terminates processing and skips remaining partition sets. An authenticated attacker with partman_user role can insert a row with a low maintenance_order value that reliably raises an exception, causing run_maintenance() to fail before processing legitimate partitions. The fix in 5.5.0 moves exception handling inside the loop to catch errors per partition set and continue processing.
Affected products
- pgpartman pg_partman before 5.5.0
Timeline
- 2026-09-18: disclosed
- 2026-07-22: patched: version 5.5.0 released