CVE-2025-2291

PgBouncer default auth_query does not take Postgres password expiry into account

Description

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

Remediation

Workaround:

  • Configure a custom auth_query containing the new default auth_query introduced in PgBouncer 1.24.1, this auth_query takes expiry into account

Category

8.1
CVSS
Severity: High
CVSS 3.1 •
EPSS 0.03%
Affected: n/a PgBouncer
Published at:
Updated at:

References

Link Tags
https://www.pgbouncer.org/changelog.html#pgbouncer-124x

Frequently Asked Questions

What is the severity of CVE-2025-2291?
CVE-2025-2291 has been scored as a high severity vulnerability.
How to fix CVE-2025-2291?
As a workaround for remediating CVE-2025-2291: Configure a custom auth_query containing the new default auth_query introduced in PgBouncer 1.24.1, this auth_query takes expiry into account
Is CVE-2025-2291 being actively exploited in the wild?
As for now, there are no information to confirm that CVE-2025-2291 is being actively exploited. According to its EPSS score, there is a ~0% probability that this vulnerability will be exploited by malicious actors in the next 30 days.
What software or system is affected by CVE-2025-2291?
CVE-2025-2291 affects n/a PgBouncer.
This platform uses data from the NIST NVD, MITRE CVE, MITRE CWE, First.org and CISA KEV but is not endorsed or certified by these entities. CVE is a registred trademark of the MITRE Corporation and the authoritative source of CVE content is MITRE's CVE web site. CWE is a registred trademark of the MITRE Corporation and the authoritative source of CWE content is MITRE's CWE web site.
© 2025 Under My Watch. All Rights Reserved.