PgBouncer · Improper Authentication
Affects pgbouncerSource GCVE Database
Not known to be exploited · CVSS 8.8 High.
Data as of 28 Oct 2026, 22:31 UTC
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 14 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
Ubuntu 26.10pgbouncerpkg:deb/ubuntu/pgbouncer?arch=source&distro=stonkingOther threats | Affected
| Fixed in– |
Ubuntu 26.04 LTSpgbouncerpkg:deb/ubuntu/pgbouncer?arch=source&distro=resoluteOther threats | Affected
| Fixed in– |
Ubuntu 24.04 LTSpgbouncerpkg:deb/ubuntu/pgbouncer?arch=source&distro=nobleOther threats | Affected
| Fixed in– |
Ubuntu 22.04 LTSpgbouncerpkg:deb/ubuntu/pgbouncer?arch=source&distro=jammyOther threats | Affected
| Fixed in– |
Ubuntu 20.04 LTSpgbouncerpkg:deb/ubuntu/pgbouncer?arch=source&distro=focalOther threats | Affected
| Fixed in– |
Ubuntu 18.04 LTSpgbouncerpkg:deb/ubuntu/pgbouncer?arch=source&distro=bionicOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
Description
Improper authentication in PgBouncer 1.17.0 through 1.26.0 allows a remote attacker who knows the password of a user listed in auth_file to log in as any other user that authenticates using SCRAM, including PgBouncer admin users and backend superusers. A second StartupMessage sent during SCRAM authentication against a non-existent database is not rejected and switches the user being logged in as, while the SCRAM exchange is still verified against the keys of the first user.