CVE-2025-2291: PgBouncer default auth_query does not take Postgres password expiry into account
First published: Wed Apr 16 2025(Updated: )
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
Credit: f86ef6dc-4d3a-42ad-8f28-e6d5547a5007
| Affected Software | Affected Version | How to fix |
|---|---|---|
| debounce |
Never miss a vulnerability like this again
Sign up to SecAlerts for real-time vulnerability data matched to your software, aggregated from hundreds of sources.
Reference Links
Frequently Asked Questions
What is the severity of CVE-2025-2291?
CVE-2025-2291 is classified as a high severity vulnerability due to the risk of unauthorized access with expired passwords.
How do I fix CVE-2025-2291?
To fix CVE-2025-2291, update PgBouncer to the latest version where the issue is resolved.
What systems are affected by CVE-2025-2291?
CVE-2025-2291 affects PgBouncer installations that do not correctly enforce password expiry based on Postgres' VALID UNTIL value.
What exploits are possible with CVE-2025-2291?
An attacker can exploit CVE-2025-2291 to log in using expired passwords, potentially gaining unauthorized access to the database.
What precautions should be taken regarding CVE-2025-2291?
Organizations should regularly update PgBouncer and review their authentication processes to ensure compliance with password expiry policies.
- collector/mitre-cve
- source/MITRE
- agent/title
- agent/references
- agent/weakness
- agent/description
- agent/first-publish-date
- agent/type
- agent/guess-ai
- agent/software-canonical-lookup
- agent/softwarecombine
- collector/nvd-api
- source/NVD
- agent/severity
- agent/author
- agent/source
- agent/last-modified-date
- agent/tags
- agent/event
- vendor/pgbouncer
- canonical/debounce