Released: 7 August 2026
Bug fixes, and security fixes in Postgres Enterprise Manager 10.5.1 include the following:
Security Fixes
| Description | Addresses |
|---|---|
Fixed CVE-2026-17566, an OS command injection vulnerability in Import/Export Data.Fixed CVE-2026-17566, an OS command injection vulnerability in Import/Export Data. | |
Fixed CVE-2026-17346, a SQL injection vulnerability in the Index Statistics and Pub/Sub views.Fixed CVE-2026-17346, a SQL injection vulnerability in the Index Statistics and Pub/Sub views. The fix for CVE-2026-12044 missed sinks allowlisted on the incorrect assumption that schema, table, publication, and subscription names from the browser tree cannot contain apostrophes. All remaining unescaped | |
Fixed CVE-2026-17351, a read-only guard lexer bypass in the AI Assistant.Fixed CVE-2026-17351, a lexer bypass in the AI Assistant's read-only guard. A payload exploiting the difference between | |
Fixed CVE-2026-17347, an OS command injection vulnerability in | |
Fixed CVE-2026-17350, a tool-permission bypass on backend routes and Socket.IO handlers.Fixed CVE-2026-17350, a tool-permission bypass on backend routes and Socket.IO handlers. Tool permissions were previously enforced only on each tool's "front door" route, while the rest of the backend relied on | |
Fixed CVE-2026-17348, a missing |
Bug Fixes
| Description | Addresses |
|---|---|
Added a watchdog thread subsystem to the PEM agent to resolve a class of bug where the agent would become unresponsive.Added a watchdog thread subsystem to the PEM agent. This thread monitors the other agent threads and can intervene if they become blocked or unresponsive. | 45933 |
Fixed an issue whereby PEM could keep sending duplicate notifications if the PEM server itself became resource-exhausted.Added a two-phase commit protocol to all four notification spoolers (SMTP, SNMP, webhook, and Nagios) to eliminate duplicate alert sends when the PEM database becomes resource-exhausted between the send and its terminal-status commit. | |
Fixed an issue whereby report templates designated for PEM servers only could be run on non-PEM servers, or on a different database, leading to errors and confusion.When a PEM report template is selected in the Run Report menu or a scheduled job step, the PEM server and database fields are now auto-selected and locked automatically. PEM reports are hidden entirely on non-PEM servers. | |
Fixed a bug whereby the PEM backend database could become overloaded by purge operations, with long-running table locks leading to false-positives "server/agent down" alerts.The purge system now deletes data in smaller batches, and the purge process is now throttled to avoid overloading the PEM backend database. This resolves a class of bugs where long-running table locks during purge operations could lead to false-positive "server/agent down" alerts. | |
Fixed a new PEM agent failing to register against a PEM server running 10.1.0.Fixed a backward-compatibility regression whereby a new PEM agent failed to register against a PEM server running 10.1.0. Also fixed SSL key and certificate paths being stored as relative rather than absolute paths during agent registration (PEM-6174). | 62259 |
Fixed a missing | |
Fixed a | |
Fixed a dashboard freeze caused by an unhandled re-render loop.Fixed a dashboard freeze caused by an unhandled re-render loop under certain widget configurations. Also fixed the Permissions panel content being obscured by an overlapping scroll area. | 60038 |
Fixed alert row expansion collapsing or jumping to the wrong row on refresh.Fixed an issue whereby alert row expansion would collapse or jump to the wrong row on data refresh. Row expansion is now bound to row identity rather than display position. | |
Fixed the expanded PgTable detail panel showing the wrong table after a sort or filter.Fixed an issue whereby the expanded PgTable detail panel showed the wrong table's details after a sort or filter. The detail panel is now bound to row identity rather than display position. | |
Fixed a | |
Fixed a |