CVE-2025-2291HighMicrosoft CVSS 8.1CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Microsoft security update for CVE-2025-2291

Published
April 23, 2025
Last Modified
—

🔗 CVE IDs covered (1)

📋 Microsoft's advisory

EchelonGraph does not copy Microsoft's advisory page: its FAQ and remediation text are not shown here. Read the advisory on https://msrc.microsoft.com/update-guide/vulnerability/CVE-2025-2291. This page also shows what EchelonGraph holds for CVE-2025-2291, with the description from its CVE record, which the CVE Numbering Authority that assigned the CVE wrote: for a CVE Microsoft assigned, often in the words of Microsoft's own advisory.

🎯 Affected products5

  • azl3 pgbouncer 1.20.1-1 on Azure Linux 3.0
  • azl3 pgbouncer 1.24.1-1 on Azure Linux 3.0
  • cbl2 pgbouncer 1.16.1-1 on CBL Mariner 2.0
  • cbl2 pgbouncer 1.16.1-1 on CBL-Mariner 2.0
  • cbl2 pgbouncer 1.24.1-1 on CBL Mariner 2.0

✅ Updates Microsoft lists: 1 update

1 row: one per KB article or update, update type and fixed build. Their details are on Microsoft's advisory.

KB articleUpdateFixed build
—Security Update1.24.1-1

🧭 EchelonGraph on CVE-2025-2291

EchelonGraph score
8.1 HIGH
CISA KEV
Not listed
Fix status
A fix is available — apply it.

Description from the CVE record (CVE.org), as published by its numbering authority

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

Published by PostgreSQL, the CVE Numbering Authority that assigned CVE-2025-2291, in its CVE record at CVE.org; reused under the CVE Program's Terms of Use (its licence and MITRE's copyright notice are in our Terms of Service).

🔗 References (2)