Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
No advisories yet.
| Link | Providers |
|---|---|
| https://www.pgbouncer.org/changelog.html#pgbouncer-125x |
|
Thu, 14 May 2026 19:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:pgbouncer:pgbouncer:*:*:*:*:*:*:*:* |
Mon, 11 May 2026 15:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Sat, 09 May 2026 02:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Pgbouncer
Pgbouncer pgbouncer |
|
| Vendors & Products |
Pgbouncer
Pgbouncer pgbouncer |
Sat, 09 May 2026 01:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | PgBouncer buffer overflow in SCRAM | |
| Weaknesses | CWE-121 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: PostgreSQL
Published:
Updated: 2026-05-12T03:55:19.823Z
Reserved: 2026-04-20T12:25:43.793Z
Link: CVE-2026-6665
Updated: 2026-05-11T14:43:15.305Z
Status : Analyzed
Published: 2026-05-09T01:16:09.013
Modified: 2026-05-14T18:52:26.537
Link: CVE-2026-6665
No data.
OpenCVE Enrichment
Updated: 2026-05-09T03:30:24Z