CVE-2026-6666: PgBouncer crash in kill_pool_logins_server_error
Published May 9, 2026
·Updated
A possible null pointer reference in PgBouncer before 1.25.2 could lead to a crash, if a server sends an error response without SQLSTATE field.
Other sources
PgBouncer crash in killpoolloginsservererror
— Microsoft
Affected Software
3 affected componentsFixes available
PgBouncer PgBouncer<1.25.2
Microsoft azl3 pgbouncer 1.25.1-1
PgBouncer PgBouncer<1.25.2
Event History
May 9, 2026
CVE Published
via MITRE·12:43 AM
Data Sourced
via MITRE·12:43 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:16 AM
DescriptionSeverityWeaknessAffected Software
May 10, 2026
Data Sourced
via Microsoft·08:01 AM
DescriptionSeverityWeakness
Data Sourced
via Microsoft·08:01 AM
Affected Software
Updated
via Microsoft·08:01 AM
DescriptionSeverity
Frequently Asked Questions
1
What is the severity of CVE-2026-6666?
CVE-2026-6666 is classified as a medium severity vulnerability due to its potential to cause service disruptions.
2
How do I fix CVE-2026-6666?
To fix CVE-2026-6666, upgrade PgBouncer to version 1.25.2 or later.
3
What are the potential impacts of CVE-2026-6666?
CVE-2026-6666 may lead to PgBouncer crashing when receiving specific error responses from the server.
4
Which versions of PgBouncer are affected by CVE-2026-6666?
CVE-2026-6666 affects all versions of PgBouncer before 1.25.2.
5
Is there a workaround for CVE-2026-6666 if I cannot upgrade?
There are no recommended workarounds for CVE-2026-6666; upgrading is the best option.