CVE-2026-6666
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA possible null pointer reference in PgBouncer before 1.25.2 could lead to a crash, if a server sends an error response without SQLSTATE field.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA null pointer dereference vulnerability in PgBouncer versions prior to 1.25.2 allows a malicious or compromised PostgreSQL server to crash the connection pooler by sending an error response that lacks the SQLSTATE field, resulting in denial of service.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 1.25.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Find PgBouncer installed versionRun 'pgbouncer --version' from command line, or check package manager output (dpkg -l pgbouncer, rpm -qi pgbouncer), or check the version displayed in PgBouncer admin console with 'SHOW VERSION;'Affected if The version returned is less than 1.25.2 (for example, 1.25.1, 1.24.0, 1.23.0, etc.)
-
Check PgBouncer process executable pathRun 'which pgbouncer' or 'ps -ef | grep pgbouncer' to identify the actual binary being used in your environmentAffected if The binary points to a versioned path containing a version number lower than 1.25.2
-
Verify running PgBouncer daemon versionConnect to PgBouncer admin database (psql -p <admin_port> -U pgbouncer -c 'SHOW VERSION;') and check the outputAffected if The reported version is below 1.25.2
If any PgBouncer instance in your environment is running version 1.25.1 or lower, the vulnerability is present and the process can crash when receiving malformed error responses from PostgreSQL servers.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.25.2
Upgrade PgBouncer to version 1.25.2 or later. If immediate patching is not feasible, restrict database server connections to trusted, controlled PostgreSQL instances to reduce the attack surface.
PgBouncer 1.25.2
- Check the currently installed PgBouncer version using 'pgbouncer --version' or your system's package manager
- Upgrade PgBouncer to version 1.25.2 or later using your system's package manager or by compiling from source from the official PgBouncer repository
- Verify the upgrade was successful by checking the installed version
- Restart the PgBouncer service to load the new version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-6666 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6666 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data