Skip to main content
VulnerabilityPublished Updated

CVE-2026-6666: PgBouncer · NULL Pointer Dereference

Affects PgBouncerSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 1.25.2 when convenient.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 30% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.25.2
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade PgBouncer to 1.25.2.

Affected software

ProductAffectedFixed in
PgBouncerAffected
  • <1.25.2
Fixed in
  • 1.25.2

AI-suggested

If you cannot patch yet, consider monitoring PgBouncer stability and error responses from backend servers to detect potential triggers. Avoid relying on untrusted or malformed error responses if possible.

Description

A 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.

References

Community reviews

Loading reviews…