CVE-2026-6667: PgBouncer before 1.25.2 did not perform an appropriate authorization check for the KILL_CLIENT admin command

Q: How do I fix CVE-2026-6667?

pgbouncer: upgrade to 1.25.2. Exact commands for each OS are on this page.

Q: Is CVE-2026-6667 being exploited?

CVE-2026-6667 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-6667 affect?

CVE-2026-6667 affects pgbouncer. Severity is medium (CVSS 4.3). PgBouncer before 1.25.2 did not perform an appropriate authorization check for the KILL_CLIENT admin command. All users with access to the administration console (which itself requires authorization) could run this command. It would have be

Q: How urgent is CVE-2026-6667?

Priority 20/100. No elevated risk signals yet.

Routine

MEDIUM 4.3UPGRADE

CVE-2026-6667 is a medium-severity flaw (CVSS 4.3) affecting pgbouncer. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

PgBouncer before 1.25.2 did not perform an appropriate authorization check for the KILL_CLIENT admin command. All users with access to the administration console (which itself requires authorization) could run this command. It would have been correct to allow only users listed in the admin_users parameter.

Why this priority

No elevated risk signals yet

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.3% (top 79%)
CISA exploited list	No
Weakness	CWE-862
Published	2026-05-09
Last modified	2026-07-24

Publisher (CNA): PostgreSQL · Vendor: pgbouncer

Last updated 2026-07-24 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-05-09 01:16 UTCPublished CVE record published
2026-07-24 08:10 UTCUpdated Record last modified

pgbouncer pgbouncer UPGRADE

Affected: < 1.25.2

Fixed in: 1.25.2

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy pgbouncer || rpm -q pgbouncer || pgbouncer --version

2. UPGRADE to 1.25.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade pgbouncer

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade pgbouncer

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-6667?

pgbouncer: upgrade to 1.25.2. Exact commands for each OS are on this page.

Is CVE-2026-6667 being exploited?

CVE-2026-6667 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-6667 affect?

CVE-2026-6667 affects pgbouncer. Severity is medium (CVSS 4.3). PgBouncer before 1.25.2 did not perform an appropriate authorization check for the KILL_CLIENT admin command. All users with access to the administration console (which itself requires authorization) could run this command. It would have be

How urgent is CVE-2026-6667?

Priority 20/100. No elevated risk signals yet.

Related CVEs

CVE-2026-6664 HIGH 7.5 UPGRADE An integer overflow in network packet parsing code in PgBouncer before 1.25.2 bypasses a boundary check and ca
CVE-2026-6665 HIGH 8.1 UPGRADE The SCRAM code in PgBouncer before 1.25.2 did not check the return value of strlcat() correctly when building
CVE-2026-6666 MEDIUM 5.9 UPGRADE A possible null pointer reference in PgBouncer before 1.25.2 could lead to a crash, if a server sends an error

References

← Back to latest CVEs