Skip to content
Fencer Intel
high 8.8

CVE-2026-107350 json

Authentication bypass via second StartupMessage during SCRAM authentication in PgBouncer

published 26d ago modified 19d ago also BIT-pgbouncer-2026-107350 , EUVD-2026-101500

cvss
8.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.4%
EPSS 0.4% chance of exploitation in 30 days, percentile 30%
public exploits
0
none known

Summary

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.

Patch / fix

  • bitnami pgbouncer 1.26.1
  • n/a PgBouncer 1.26.1
  • pgbouncer Debian 14 1.26.1-1

debian advisories DEBIAN-CVE-2026-107350

  • pgbouncer hummingbird 1 1.26.1-1.hum1

red hat advisories RHSA-2026:83843

  • pgbouncer Azure Linux 3.0 1.26.1-1

azure linux advisories AZL-108189

Azure Linux vulnerability data, Copyright (c) Microsoft Corporation, from https://github.com/microsoft/AzureLinuxVulnerabilityData via OSV, under the MIT licence; changed: normalised to fixed package versions per release. MIT

Is CVE-2026-107350 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-107350 updated cvss 8.8

pgbouncer: pgbouncer: Privilege escalation via secondary startup message during SCRAM authentication

  • Red Hat Hardened Images pgbouncer 1.26.1-1.hum1
    fixed: vendor fix RHSA-2026:83843

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
24d ago

Exploit prediction

0.37% chance of exploitation in the next 30 days, higher than 30% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
OSV 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected packages

ecosystem package affected fixed in
bitnami pgbouncer
>=1.17.0, <1.26.1
1.26.1

Affected products

  • n/a PgBouncer

Classification

Weakness

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.