Cyber Resilience

CVE-2025-2291

Pgbouncer ≤ 1.24.1

Published
16 April 2025
Modified
08 December 2025
CVSS Score v3.1 8.1
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS Score 0.0034 27th percentile
Risk Priority 59 floored blend · peak EPSS

Summary

CVE-2025-2291 is a high-severity Use of a Key Past its Expiration Date (CWE-324) vulnerability in Pgbouncer Pgbouncer. Its CVSS base score is 8.1 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Brute Force (T1110); ranked at the 27th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to IA-5 (Authenticator Management) and SC-12 (Cryptographic Key Establishment and Management) — see the control section below for these in your framework.

OWASP Top 10 for Web (2025)

A04:2025 Cryptographic Failures

EU & UK References

Vulnerability Data

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

CWE(s)
CWE-324

Related Threats

MITRE ATT&CK Enterprise Techniques

T1110 Brute Force Credential Access
Adversaries may use brute force techniques to gain access to accounts when passwords are unknown or when password hashes are obtained.
attack.mitre.org →
T1110.002 Password Cracking Credential Access
Adversaries may use password cracking to attempt to recover usable credentials, such as plaintext passwords, when credential material such as password hashes are obtained.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2025-13723Shared CWE-324
CVE-2024-7318Shared CWE-324
CVE-2025-48813Shared CWE-324
CVE-2024-25679Shared CWE-324
CVE-2024-6299Shared CWE-324
CVE-2025-31123Shared CWE-324
CVE-2024-36031Shared CWE-324
CVE-2025-33012Shared CWE-324
CVE-2026-39923Shared CWE-324
CVE-2026-6664Same product: Pgbouncer Pgbouncer

Affected Assets

pgbouncer
pgbouncer
≤ 1.24.1
debian
debian linux
11.0

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SC-12 Cryptographic Key Establishment and Management good match

SC-12 requires establishing and managing cryptographic keys including distribution, storage, access and destruction, which directly enforces expiration and rotation policies.

IA-5 Authenticator Management good match

IA-5 requires managing authenticators (including passwords and tokens) with verification, distribution and revocation steps that cover expiration enforcement.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

ID.AM-08 partial match
prevents

Lifecycle management of cryptographic assets directly includes enforcing key expiration and rotation.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.24 Use of cryptography mostly match
prevents

Use-of-cryptography control explicitly covers key lifecycle management including expiration and rotation.

A.5.17 Authentication information partial match
prevents

Authentication information policy should mandate key rotation and expiry, directly preventing use of expired keys.

A.8.32 Change management partial match
mitigates

Change-management processes can trigger key rotation, but do not inherently enforce cryptographic expiry rules.

A.8.5 Secure authentication partial match
degrades

Secure authentication requires cryptographic keys to be replaced before expiry, mitigating the weakness.

References