CVE-2026-6665

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 69% of all CVEs by exploit prediction. GitHub Security Advisory enrichment pending alignment with NVD CVSS.

Triggered by: NVD CVSS baseline
Sources: epss, ghsa, nvd
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 9.8Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The SCRAM code in PgBouncer before 1.25.2 did not check the return value of strlcat() correctly when building the contents of the SCRAM client-final-message. A malicious backend that sends a SCRAM server-final-message with a long nonce can trigger a stack overflow.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
44(Track)
EG Risk 44/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

May 9, 2026

Last Modified

July 24, 2026

Advisory Details (1)

Auto-updated Sep 4, 2026
No patch confirmed yet.
generic

PgBouncer changelog

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

Vendor Advisories for CVE-2026-6665(1)

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

Affected Packages

(4 across 4 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
pgbouncer1.15.0-1 ... 1.25.2-1 (26 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
pgbouncer1.18.0-1 ... 1.25.2-1 (18 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
pgbouncer1.24.1-1, 1.24.1-1+deb13u11.24.1-1+deb13u2—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
pgbouncer1.24.1-1, 1.25.0-1, 1.25.0-2, 1.25.1-11.25.2-1—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 6× in last 7d / 111× 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.

Showing the most recent 100 of 309 total refreshes for this CVE.

  1. 2026-09-04 05:07 UTCEPSS rescore
  2. 2026-09-02 14:12 UTCEPSS rescore
  3. 2026-09-01 13:54 UTCEPSS rescore
  4. 2026-09-01 04:40 UTCEPSS rescore
  5. 2026-08-30 19:17 UTCEPSS rescore
  6. 2026-08-30 01:22 UTCEPSS rescore
  7. 2026-08-28 21:42 UTCEPSS rescore
  8. 2026-08-26 14:47 UTCEPSS rescore
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-23 18:51 UTCEG score recompute
  11. 2026-08-23 18:51 UTCVendor advisory
  12. 2026-08-23 18:51 UTCGHSA enrichment
  13. 2026-08-23 00:19 UTCEPSS rescore
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-20 22:56 UTCEPSS rescore
  16. 2026-08-19 17:04 UTCEPSS rescore
  17. 2026-08-18 13:49 UTCEPSS rescore
  18. 2026-08-18 13:49 UTCEPSS rescore
  19. 2026-08-17 13:47 UTCEPSS rescore
  20. 2026-08-17 11:28 UTCEG score recompute
  21. 2026-08-17 11:28 UTCVendor advisory
  22. 2026-08-17 11:28 UTCGHSA enrichment
  23. 2026-08-16 14:56 UTCEPSS rescore
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 08:49 UTCVendor advisory
Show 75 more
  1. 2026-08-16 08:49 UTCGHSA enrichment
  2. 2026-08-16 04:31 UTCEG score recompute
  3. 2026-08-16 04:31 UTCVendor advisory
  4. 2026-08-16 04:31 UTCGHSA enrichment
  5. 2026-08-16 02:15 UTCEPSS rescore
  6. 2026-08-15 01:31 UTCEPSS rescore
  7. 2026-08-15 00:33 UTCVendor advisory
  8. 2026-08-15 00:33 UTCGHSA enrichment
  9. 2026-08-14 20:16 UTCVendor advisory
  10. 2026-08-14 20:16 UTCGHSA enrichment
  11. 2026-08-14 15:58 UTCVendor advisory
  12. 2026-08-14 15:58 UTCGHSA enrichment
  13. 2026-08-14 11:40 UTCVendor advisory
  14. 2026-08-14 11:40 UTCGHSA enrichment
  15. 2026-08-14 07:23 UTCVendor advisory
  16. 2026-08-14 07:23 UTCGHSA enrichment
  17. 2026-08-14 03:05 UTCEG score recompute
  18. 2026-08-14 03:05 UTCVendor advisory
  19. 2026-08-14 03:05 UTCGHSA enrichment
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 10:48 UTCVendor advisory
  22. 2026-08-13 10:48 UTCGHSA enrichment
  23. 2026-08-13 05:58 UTCVendor advisory
  24. 2026-08-13 05:58 UTCGHSA enrichment
  25. 2026-08-13 01:16 UTCGHSA enrichment
  26. 2026-08-12 20:59 UTCGHSA enrichment
  27. 2026-08-12 16:41 UTCEG score recompute
  28. 2026-08-12 16:41 UTCVendor advisory
  29. 2026-08-12 16:41 UTCGHSA enrichment
  30. 2026-08-12 13:51 UTCEPSS rescore
  31. 2026-08-12 00:29 UTCVendor advisory
  32. 2026-08-12 00:29 UTCGHSA enrichment
  33. 2026-08-11 20:08 UTCVendor advisory
  34. 2026-08-11 20:08 UTCGHSA enrichment
  35. 2026-08-11 15:50 UTCEG score recompute
  36. 2026-08-11 15:50 UTCVendor advisory
  37. 2026-08-11 15:50 UTCGHSA enrichment
  38. 2026-08-11 10:11 UTCVendor advisory
  39. 2026-08-11 10:11 UTCGHSA enrichment
  40. 2026-08-11 05:32 UTCVendor advisory
  41. 2026-08-11 05:32 UTCGHSA enrichment
  42. 2026-08-11 01:15 UTCEG score recompute
  43. 2026-08-11 01:15 UTCVendor advisory
  44. 2026-08-11 01:15 UTCGHSA enrichment
  45. 2026-08-11 00:00 UTCEPSS rescore
  46. 2026-08-10 12:43 UTCVendor advisory
  47. 2026-08-10 12:43 UTCGHSA enrichment
  48. 2026-08-10 08:25 UTCGHSA enrichment
  49. 2026-08-10 04:08 UTCVendor advisory
  50. 2026-08-10 04:08 UTCGHSA enrichment
  51. 2026-08-09 23:50 UTCGHSA enrichment
  52. 2026-08-09 19:33 UTCVendor advisory
  53. 2026-08-09 19:33 UTCGHSA enrichment
  54. 2026-08-09 15:15 UTCEG score recompute
  55. 2026-08-09 15:15 UTCGHSA enrichment
  56. 2026-08-09 13:47 UTCEPSS rescore
  57. 2026-08-09 10:58 UTCVendor advisory
  58. 2026-08-09 10:58 UTCGHSA enrichment
  59. 2026-08-09 06:39 UTCGHSA enrichment
  60. 2026-08-09 02:21 UTCEG score recompute
  61. 2026-08-09 02:21 UTCVendor advisory
  62. 2026-08-09 02:21 UTCGHSA enrichment
  63. 2026-08-08 16:37 UTCEPSS rescore
  64. 2026-08-08 10:02 UTCVendor advisory
  65. 2026-08-08 10:02 UTCGHSA enrichment
  66. 2026-08-08 05:44 UTCGHSA enrichment
  67. 2026-08-08 01:27 UTCVendor advisory
  68. 2026-08-08 01:27 UTCGHSA enrichment
  69. 2026-08-07 21:09 UTCGHSA enrichment
  70. 2026-08-07 16:52 UTCEG score recompute
  71. 2026-08-07 16:52 UTCVendor advisory
  72. 2026-08-07 16:52 UTCGHSA enrichment
  73. 2026-08-07 12:34 UTCVendor advisory
  74. 2026-08-07 12:34 UTCGHSA enrichment
  75. 2026-08-07 08:16 UTCVendor advisory

Frequently asked(5)

What is CVE-2026-6665?
CVE-2026-6665 is a critical vulnerability published on May 9, 2026. The SCRAM code in PgBouncer before 1.25.2 did not check the return value of strlcat() correctly when building the contents of the SCRAM client-final-message. A malicious backend that sends a SCRAM server-final-message with a long nonce can trigger a stack overflow.
When was CVE-2026-6665 disclosed?
CVE-2026-6665 was first published in the National Vulnerability Database on May 9, 2026, with the most recent update on July 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6665 actively exploited?
CVE-2026-6665 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 69.7% of all scored CVEs.
What is the CVSS score of CVE-2026-6665?
CVE-2026-6665 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-6665?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6665, 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-6665

Explore →

Is Your Infrastructure Affected by CVE-2026-6665?

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

Start Free Scan →Browse All CVEs