ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2026-6665

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.

Published May 9, 2026 · catalog updated Jul 24, 2026 · The SCRAM code in

Check if you run it

No confirmed exploitation is on record for CVE-2026-6665. EPSS is 0.44%. Act only if a listed version of The SCRAM code in is installed.

Gaps on this record

  • The stored product name is a package slug. The name on this page is taken from the title (The SCRAM code in).
  • No version range is stored. A customer cannot check an installed version against this record.
  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Critical9.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.44%
Remediation
Not established
Affected products
cpe pgbouncer/pgbouncer

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • cpe pgbouncer/pgbouncerversion unspecified

How to fix CVE-2026-6665

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2026-6665. EPSS is 0.44%. Act only if a listed version of The SCRAM code in is installed.

Which versions are affected?

Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

CWE-121: Stack-based Buffer Overflow. EPSS 0.44%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. May 9, 2026 · NIST NVD

    Detected

    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.

  2. Jul 24, 2026 · NIST NVD

    Updated

    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.

Sources

  • CVE.orgVulnerability recordCVE-2026-6665

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2026-6665

    30-day exploitation probability 0.4%

    first.org
  • NIST NVDVulnerability recordCVE-2026-6665

    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.

    nvd.nist.gov

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.