Authentication bypass via expiry-blind password lookup
Published Apr 16, 2025 · Updated Nov 3, 2025
Authentication bypass in PgBouncer before 1.24.1 allows remote attackers to log in through the proxy with an expired PostgreSQL password. The default auth_query returns rolpassword from pg_authid without checking rolvaliduntil, so PgBouncer accepts a hash that PostgreSQL treats as expired. Exposure requires auth_user with the default or a similarly unsafe custom auth_query and a valid password whose VALID UNTIL time has passed.
Summary
What happened
Authentication bypass in PgBouncer before 1.24.1 allows remote attackers to log in through the proxy with an expired PostgreSQL password. The default auth_query returns rolpassword from pg_authid without checking rolvaliduntil, so PgBouncer accepts a hash that PostgreSQL treats as expired. Exposure requires auth_user with the default or a similarly unsafe custom auth_query and a valid password whose VALID UNTIL time has passed.
The record
- CVE
- CVE-2025-2291
- Published
- Apr 16, 2025
- Updated
- Nov 3, 2025
- Vendor
- PgBouncer
- Product
- PgBouncer
- Classifications
- CWE-324, T1078
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 16, 2025CVE publishedPublication date reported by the CVE source.
- Nov 3, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <1.24.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo