CVE-2026-6666

MEDIUMNVD 5.95.9—Trending — 4 sources updated this week

5.9

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.

CVSS v3: 5.9
EG Score: 5.9(medium)
EPSS: 4.3%
KEV: Not listed

Published

May 9, 2026

Last Modified

May 14, 2026

Advisory Details (1)

Auto-updated May 9, 2026

No patch confirmed yet.

generic

PgBouncer changelog

https://www.pgbouncer.org/changelog.html#pgbouncer-125x

Vendor Advisories for CVE-2026-6666(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

CVE-2026-6666
Microsoft Security Response Center (MSRC)Medium
PgBouncer crash in kill_pool_logins_server_error

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

CWE-476NULL Pointer Dereference

Data Freshness Timeline

(refreshed 20× in last 7d / 20× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

2026-06-09 15:29 UTCEG score recompute
2026-06-09 15:29 UTCVendor advisory
2026-06-09 15:29 UTCGHSA enrichment
2026-06-08 14:30 UTCEG score recompute
2026-06-08 14:30 UTCVendor advisory
2026-06-08 14:30 UTCGHSA enrichment
2026-06-08 14:17 UTCEPSS rescore
2026-06-07 15:25 UTCEPSS rescore
2026-06-07 13:31 UTCEG score recompute
2026-06-07 13:31 UTCVendor advisory
2026-06-07 13:31 UTCGHSA enrichment
2026-06-06 13:47 UTCEPSS rescore
2026-06-06 12:32 UTCEG score recompute
2026-06-06 12:32 UTCVendor advisory
2026-06-06 12:32 UTCGHSA enrichment
2026-06-05 22:47 UTCEPSS rescore
2026-06-05 11:32 UTCEG score recompute
2026-06-05 11:32 UTCVendor advisory
2026-06-05 11:32 UTCGHSA enrichment
2026-06-05 06:10 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-6666?

CVE-2026-6666 is a medium vulnerability published on May 9, 2026. 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.

When was CVE-2026-6666 disclosed?

CVE-2026-6666 was first published in the National Vulnerability Database on May 9, 2026, with the most recent update on May 14, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2026-6666 actively exploited?

CVE-2026-6666 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 4.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2026-6666?

CVE-2026-6666 has a CVSS v3 base score of 5.9 (NVD).

How do I remediate CVE-2026-6666?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6666, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6666

Explore →

Is Your Infrastructure Affected by CVE-2026-6666?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2026-6666

📅 Published

🔄 Last Modified

📋 Advisory Details (1)