> ## Content Index
> Fetch the complete content index at: https://www.stirup.si/llms.txt
> Use this file to discover other available public pages before exploring further.

# Pgpool-II 4.7.3, 4.6.8, 4.5.13, 4.4.18 and 4.3.21 released
- URL: https://www.stirup.si/pgpool-ii-4-7-3-4-6-8-4-5-13-4-4-18-and-4-3-21-released-3facdd84/
- Published: 2026-10-12T00:34:47.000Z
- Updated: 2026-10-12T00:34:47.000Z
- Description: Pgpool-II has released several minor versions with critical security updates addressing multiple vulnerabilities. These updates are essential for maintaining the integrity and reliability of PostgreSQL clusters using Pgpool-II.
- Author: Satish Das
- Tags: Data, Stirup Research

## Overview of Pgpool-II Security Releases

Pgpool-II, a widely used tool for enhancing PostgreSQL with features like connection pooling, load balancing, and automatic failover, has released several minor versions to address critical security vulnerabilities. The latest versions include 4.7.3, 4.6.8, 4.5.13, 4.4.18, and 4.3.21\. These updates are crucial for users relying on Pgpool-II to manage PostgreSQL clusters securely and efficiently.

## Security Vulnerabilities Addressed

The released versions include fixes for multiple vulnerabilities that could allow attackers to exploit weaknesses in Pgpool-II's watchdog message processing, certificate authentication handling, and inter-node communication. These vulnerabilities, identified as CVE-2026-92867 through CVE-2026-92873, pose significant risks to systems using Pgpool-II for high-availability PostgreSQL setups.

One of the vulnerabilities allows an attacker to write arbitrary 32-bit values to memory addresses by sending malformed watchdog messages. Another vulnerability in certificate authentication processing could enable a malicious client to impersonate another user without requiring a password. These issues highlight the importance of applying the latest security patches promptly.

## Implications for Users

Users of Pgpool-II should prioritize upgrading to the latest versions to mitigate the risks associated with these vulnerabilities. The updates are particularly important for environments where Pgpool-II is used in production, as unpatched systems could be exposed to potential exploitation by malicious actors.

While the release notes do not provide detailed performance improvements or new features, the focus on security in these updates underscores the ongoing commitment of the Pgpool Global Development Group to maintaining the reliability and safety of the tool. Users are encouraged to review the release notes for specific details on the changes included in each version.

## Conclusion

The release of these minor versions of Pgpool-II is a necessary step to address critical security issues. Organizations using Pgpool-II should ensure that their systems are updated to the latest versions to protect against potential threats. As with any software update, it is advisable to test the new versions in a staging environment before deploying them in production to ensure compatibility and stability.

**Source:** [PostgreSQL](https://www.postgresql.org/about/news/pgpool-ii-473-468-4513-4418-and-4321-released-3390/?ref=stirup.si). Analysis based on publicly available information; no hands-on testing is claimed.