p PatchFirst

PatchFirst · Vulnerabilidades recientes

Vulnerabilidades de pgbouncer

Vulnerabilidades publicadas para pgbouncer en los últimos 30 días: 3. Incluidas en el catálogo KEV: 0.

RSS ↗
Filtrar vulnerabilidades
Borrar filtros

Vulnerabilidades: 16

  1. CVE-2026-107350

    Alta · CVSS 8.8EPSS 0,36%Corrección disponible

    Authentication bypass via second StartupMessage during SCRAM authentication in PgBouncer

    Improper authentication in PgBouncer 1.17.0 through 1.26.0 allows a remote attacker who knows the password of a user listed in auth_file to log in as any other user that authenticates using SCRAM, including PgBouncer admin users and backend superusers. A second StartupMessage sent during SCRAM authentication against a non-existent database is not rejected and switches the user being logged in as, while the SCRAM exchange is still verified against the keys of the first user.

    pgbouncerSistemas operativos
    • Actualiza a 1.26.1-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗

  2. CVE-2026-107349

    Alta · CVSS 7.5EPSS 0,42%Corrección disponible

    Infinite loop on empty option name in startup options parameter in PgBouncer

    An infinite loop in PgBouncer 1.20.0 through 1.26.0 allows an unauthenticated remote attacker to cause a denial of service. A StartupMessage whose options parameter contains an empty parameter name, such as "-c=", makes the ignore_startup_parameters list lookup loop forever. Because PgBouncer serves all clients from a single process, this saturates a CPU core and makes PgBouncer unresponsive to all clients until the process is restarted.

    pgbouncerSistemas operativos
    • Actualiza a 1.26.1-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗

  3. CVE-2026-107348

    Media · CVSS 5.9EPSS 0,39%Corrección disponible

    Integer overflow causes an infinite loop in message buffer growth in PgBouncer

    Integer overflow in the message buffer growth logic (mbuf_make_room) in PgBouncer 1.21.0 through 1.26.0 allows a remote attacker to cause a denial of service when max_packet_size is configured above 2147483648. A packet header declaring a length above 2^31 makes the buffer size computation overflow, leaving the growth loop unable to terminate. Because PgBouncer serves all clients from a single process, this saturates a CPU core and stalls every pooled connection until the process is restarted. Since 1.23.0 the overflow is reachable before authentication with a five-byte packet header.

    pgbouncerSistemas operativos
    • Actualiza a 1.26.1-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗

  4. CVE-2026-19888

    Alta · CVSS 7.5EPSS 0,39%Corrección disponible

    NULL pointer dereference in SCRAM client-final-message parsing in PgBouncer

    Missing validation of a mandatory attribute in the SCRAM client-final-message parser in PgBouncer through 1.25.2 allows an unauthenticated remote attacker to crash the process. A malformed message can make the parser report success while leaving a required value unset, which is then dereferenced as a NULL pointer. The crash occurs before any credential is verified, so no valid account is required. Because PgBouncer serves all clients from a single process, this terminates every pooled connection.

    pgbouncerSistemas operativos
    • Actualiza a 1.26.0-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗

  5. CVE-2026-6669

    Media · CVSS 5.9EPSS 0,31%Corrección disponible

    Unbounded SCRAM iteration count causes CPU exhaustion in PgBouncer

    Missing upper bound on the key derivation iteration count accepted during SCRAM authentication to a backend server in PgBouncer through 1.25.2 allows a malicious or compromised PostgreSQL backend to cause uncontrolled CPU consumption in PgBouncer. The resulting key derivation cannot be interrupted in frontend builds such as PgBouncer. Because PgBouncer serves all clients from a single process, one backend can in this way stop it from serving traffic for every other database and client it is pooling, so the failure of a single backend is not contained.

    pgbouncerSistemas operativos
    • Actualiza a 1.26.0-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗

  6. CVE-2026-6668

    Alta · CVSS 7.5EPSS 0,4%Corrección disponible

    Integer overflow causes an infinite loop in packet buffer growth in PgBouncer

    Integer overflow in the packet buffer growth logic in PgBouncer through 1.25.2 allows an unauthenticated remote attacker to cause a denial of service. Sufficiently large input makes the buffer size computation overflow, leaving the growth loop unable to terminate. Because PgBouncer serves all clients from a single process, this saturates a CPU core and stalls every pooled connection until the process is killed. Both unauthenticated and authenticated code paths can reach the overflow.

    pgbouncerSistemas operativos
    • Actualiza a 1.26.0-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗

  7. CVE-2026-6667

    Media · CVSS 4.3EPSS 0,33%Corrección disponible

    PgBouncer missing authorization check in KILL_CLIENT admin command

    PgBouncer before 1.25.2 did not perform an appropriate authorization check for the KILL_CLIENT admin command. All users with access to the administration console (which itself requires authorization) could run this command. It would have been correct to allow only users listed in the admin_users parameter.

    pgbouncerSistemas operativos
    • Actualiza a 1.25.2-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗

  9. CVE-2026-6665

    Alta · CVSS 8.1EPSS 0,44%Corrección disponible

    PgBouncer buffer overflow in SCRAM

    The SCRAM code in PgBouncer before 1.25.2 did not check the return value of strlcat() correctly when building the contents of the SCRAM client-final-message. A malicious backend that sends a SCRAM server-final-message with a long nonce can trigger a stack overflow.

    pgbouncerSistemas operativos
    • Actualiza a 1.25.2-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗

  10. CVE-2026-6664

    Alta · CVSS 7.5EPSS 0,73%Corrección disponible

    PgBouncer integer overflow in PgBouncer network packet parsing

    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.

    pgbouncerSistemas operativos
    • Actualiza a 1.25.2-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗

  11. CVE-2025-12819

    Alta · CVSS 7.5EPSS 0,36%Corrección disponible

    Untrusted search path in auth_query connection in PgBouncer

    Untrusted search path in auth_query connection handler in PgBouncer before 1.25.1 allows an unauthenticated attacker to execute arbitrary SQL during authentication via a malicious search_path parameter in the StartupMessage.

    pgbouncerSistemas operativos
    • Actualiza a 1.25.1-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  12. CVE-2025-2291

    Alta · CVSS 8.1EPSS 0,37%Corrección disponible

    PgBouncer default auth_query does not take Postgres password expiry into account

    Password can be used past expiry in PgBouncer due to auth_query not taking into account Postgres its VALID UNTIL value, which allows an attacker to log in with an already expired password

    pgbouncerSistemas operativos
    • Actualiza a 1.24.1-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

  13. CVE-2021-3935

    Alta · CVSS 8.1EPSS 1,12%Corrección disponible

    CVE-2021-3935

    When PgBouncer is configured to use "cert" authentication, a man-in-the-middle attacker can inject arbitrary SQL queries when a connection is first established, despite the use of TLS certificate verification and encryption. This flaw affects PgBouncer versions prior to 1.16.1.

    pgbouncerSistemas operativos
    • Actualiza a 1.16.1-1
    Publicación Actualización
    Aviso original 1 ↗Aviso original 2 ↗Aviso original 3 ↗

Comprueba tu servidor

Compara tu pila y las versiones instaladas con las bases actuales de vulnerabilidades.

Comprueba tu servidor →