CVE-2026-6664
Received Received - Intake
Integer Overflow in PgBouncer Leads to Denial of Service

Publication date: 2026-05-09

Last updated on: 2026-05-09

Assigner: PostgreSQL

Description
An integer overflow in network packet parsing code in PgBouncer before 1.25.2 bypasses a boundary check and can lead to a crash. An unauthenticated remote attacker can crash PgBouncer with a malformed SCRAM authentication packet.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-09
Last Modified
2026-05-09
Generated
2026-05-29
AI Q&A
2026-05-09
EPSS Evaluated
2026-05-28
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
pgbouncer pgbouncer to 1.25.2 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-190 The product performs a calculation that can produce an integer overflow or wraparound when the logic assumes that the resulting value will always be larger than the original value. This occurs when an integer value is incremented to a value that is too large to store in the associated representation. When this occurs, the value may become a very small or negative number.
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability described is an integer overflow in PgBouncer that allows an unauthenticated remote attacker to crash the service, causing a denial of service.

Since the vulnerability leads to availability impact (crash) but does not affect confidentiality or integrity, its direct impact on compliance with standards like GDPR or HIPAAβ€”which primarily focus on protecting personal data confidentiality and integrityβ€”is limited.

However, denial of service could indirectly affect compliance if it disrupts access to critical systems or data required for regulatory obligations.


Can you explain this vulnerability to me?

This vulnerability is an integer overflow in the network packet parsing code of PgBouncer versions before 1.25.2. It bypasses a boundary check, which can cause the software to crash when it processes a malformed SCRAM authentication packet.

An unauthenticated remote attacker can exploit this flaw to crash PgBouncer by sending a specially crafted SCRAM authentication packet.


How can this vulnerability impact me? :

The primary impact of this vulnerability is a denial of service (DoS) condition, where an attacker can cause PgBouncer to crash remotely without authentication.

This can disrupt database connection pooling services, potentially causing downtime or degraded performance for applications relying on PgBouncer.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart