# CVE-2026-6667: PgBouncer missing authorization check in KILL_CLIENT admin command

> Attackers with admin console access can disconnect arbitrary clients via the KILL_CLIENT command, causing denial of service.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 May 2026
- **Updated:** 11 May 2026
- **Also known as:** AZL-86240, BIT-pgbouncer-2026-6667, CLEANSTART-2026-KP55848, DEBIAN-CVE-2026-6667, GHSA-gc77-jrv9-6fjp, MINI-cr3h-9hgx-hr78, UBUNTU-CVE-2026-6667

## What is CVE-2026-6667?

CVE-2026-6667 is a medium-severity missing authorization vulnerability in PgBouncer, published on 9 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-6667?

1 open source package ship an affected version, including pgbouncer. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pgbouncer` | Bitnami | All versions | 1.25.2 |

Products: Pgbouncer Pgbouncer.

## How do I fix CVE-2026-6667?

Upgrade pgbouncer to 1.25.2 or later.

## Is CVE-2026-6667 being exploited?

There is no known exploitation of CVE-2026-6667 in the wild and no public exploit code.

## Other vulnerabilities in PgBouncer

- [CVE-2026-6665](https://insights.sbomify.com/CVE-2026-6665/): PgBouncer buffer overflow in SCRAM (high 8.1)
- [CVE-2015-6817](https://insights.sbomify.com/CVE-2015-6817/): Auth bypass in n/a (high 8.1)
- [CVE-2026-6664](https://insights.sbomify.com/CVE-2026-6664/): PgBouncer integer overflow in PgBouncer network packet parsing (high 7.5)
- [CVE-2025-12819](https://insights.sbomify.com/CVE-2025-12819/): Untrusted search path in auth_query connection in PgBouncer (high 7.5)
- [CVE-2015-4054](https://insights.sbomify.com/CVE-2015-4054/): Null dereference in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-6667 and fix it if it is affected.

What it is: CVE-2026-6667 is a medium-severity missing authorization vulnerability in PgBouncer, published on 9 May 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-6667 in the wild and no public exploit code.

Affected packages and fixed versions:
- pgbouncer (Bitnami): affected all versions; fixed in 1.25.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-6667/ (Markdown: https://insights.sbomify.com/CVE-2026-6667/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-6667
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-6667
- OSV: https://osv.dev/vulnerability/CVE-2026-6667

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-6667/
Summaries are generated and may contain mistakes; the official description above is the record.