This vulnerability involves a use-after-free condition in pglogical's worker signaling code, where a worker structure is dereferenced after its associated slot has been freed or recycled. The flaw is reachable during normal replication operations and can be influenced by a low-privileged user through permitted pglogical operations affecting worker lifecycle timing. The primary consequence is crashing replication workers, impacting availability. More critically, exploitation could lead to remote code execution within the PostgreSQL backend context, elevating the severity of the issue.

The vulnerability can cause replication workers to crash, resulting in availability disruptions of the replication service. Additionally, it poses a high-severity risk as it may be exploited to achieve remote code execution with the privileges of the PostgreSQL backend process, potentially compromising the entire database system.

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. No official fix or temporary workaround has been documented at this time. Users should monitor EnterpriseDB advisories for updates and apply patches promptly once available. Until then, carefully controlling access to pglogical operations that influence worker lifecycle timing may reduce risk.