CVE-2026-6665

HIGHNVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-05-09. NVD baseline CVSS 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
8.1
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 8.1Exploit: NoneExposed: 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
8.1
EG Score
8.1(medium)
EPSS
29.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-6665(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 61× 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 173 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-6665?
CVE-2026-6665 is a high 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 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-6665 actively exploited?
CVE-2026-6665 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 29.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-6665?
CVE-2026-6665 has a CVSS v3 base score of 8.1 (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

Explore the affected products and dependency analysis for 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